Upsizing to SQL Server
Do you have an existing database application that is creaking at the seams?
Perhaps an Access/JET application which runs so slow as to be almost unusable or
corrupts all too frequently? An old DOS Paradox system that needs to work with
other modern programs? Or maybe you need to extend a database to the Internet?
If you are in this situation then you should consider migrating your system
to a client/server architecture such as is provided by SQL Server. For a
discussion about the differences between a File Sharing system, such as
Access/Paradox/Foxpro/FileMaker/etc, and a Client/Server architecture such as
SQL Server/DB2/Oracle please click here.
Most people want to know how much it will cost to migrate their database to
SQL Server, how long it will take and how much faster it will run afterwards.
Unfortunately these are all of the 'how long is a piece of string' type of
question. We broadly divide migrating a database to SQL Server into three main
categories:
Although going through the upsize process can be a daunting task, the
benefits from the efforts are definitely worth the while and will have a
immediate ROI. We optimize the process, by concentrating especially on areas where you are having
performance issues and on the screens that are used frequently. The top two
types of benefits often include:
Speed Improvements
Overall speed improvements are very difficult to predict
as it all depends upon how slow the system is to start with! On most Access
systems we would expect at least a three fold increase in overall speed but for
some areas it can be literally hundreds of times faster! Where the application
has been fully upsized to SQL Server we would expect most forms to open within a
second or so (i.e. performance is not usually an issue).
Reliability Improvements
It is very rare to experience crashes or corruption
of SQL Server databases and reliability is at least several orders of magnitude
better than Access/JET. With Access/JET a catastrophic failure usually means
that you must fall back to the previous night's backup and hence lose the last
day's data. With a correctly set-up SQL Server backup regime including custom
log shipping we can usually restrict loss of data to a maximum of 10 minutes
(and normally with no data loss at all). Failover support can also be
implemented, but this is a more expensive solution only suitable for those with
deep pockets.
There is no simple answer if you wish to know what will be
involved in upsizing your database to SQL Server. It all depends..... upon why
you are upsizing.... what your existing computing infrastructure is like....
what your future plans are.... how much money you have in the budget and of how
much business advantage will be gained by converting. |