SQL Server Upgrade Consulting
Upgrading to SQL Server 2005 or 2008
SQL Server 2000 may work just great but there comes
a time when upgrading to a new version becomes necessary. It may be
because of the need for assured support and security fixes or for access
to a new feature, or for better performance. What ever the reason you may
want some help preparing and executing a SQL Server upgrade.
Each upgrade starts with a review of the current
configuration, code, and any existing plans. It's important to evaluate:
Application connection options
Which version to upgrade to? 32-bit
What new features will be used immediately
Is an edition change possible or even required?
It's important to take a look at the SQL Server
objects such as tables, views, stored procs, and functions. Will the
migrate cleanly? Is recoding necessary because they use deprecated
features? For example, this query using the old join syntax:
(Quantity * Price)
from OrderHeader ,OrderDetail
Gives this error message:
Msg 4147, Level 15, State 1, Line 6
The query uses non-ANSI outer join
operators ("*=" or "=*"). To run this query without modification, please set the
compatibility level for current database to 80, using the SET
COMPATIBILITY_LEVEL option of ALTER DATABASE. It is strongly recommended to
rewrite the query using ANSI outer join operators (LEFT OUTER JOIN, RIGHT OUTER
JOIN). In the future versions of SQL Server, non-ANSI join operators will not be
supported even in backward-compatibility modes.
Either this code has to be changed or the database
must be run in a backwards compatibility mode, possibly limiting the use of new
The evaluation is followed by a plan and then an
implementation. These have to be created to fit into your operational
requirements and budget.
If you're looking for this type of help, please
call Andrew Novick at 978-440-8126 or email anovick @ novicksoftware.com
for information on other Novick Software projects.
SQL Server 2000
SQL Server 2005
SQL Server 2008
SQL Server 7