How to Migrate Databases of Different SQL Server Versions

November 30th, 2009

Need to move databases from SQL Server 2000 to SQL Server 2005 – 2008 or vice versa?

dbForge Schema Compare for SQL Server can successfully do any of these tasks. This tool generates a script in the same syntax that is used by the Target database. For example, if the Target database is on SQL Server 2000, User-Defined Data Type in the script will be written like EXEC sp_addtype ‘State’, ‘bit’, ‘NOT NULL’, whereas for SQL Server 2005 (or SQL Server 2008), it could be CREATE TYPE dbo.[State] FROM bit NOT NULL.

Create UDDT

Different syntax

But how about some data types and objects appeared in latest SQL Server versions? For example, tables containing columns of time data type have no matches in SQL Server 2000.

How will they be converted? Such objects will get Inconsistent status and won’t be included into synchronization.

Inconsistant Object

Inconsistent Object

Some objects, mainly containing custom code, such as stored procedures and functions, may have incompatibility in their syntax. This will require conversion of Target database into other compatibility level, for example, 80. dbForge Schema Compare for SQL Server doesn’t control incompatibility of such objects, so you need to analyze your databases for these conditions before synchronization.

Learn more and get a free 30-day evaluation of dbForge Schema Compare for SQL Server.

Moreover, you can take full advantage of data and schema synchronization functionality in dbForge Compare Bundle that includes both dbForge Data Compare for SQL Server and dbForge Schema Compare for SQL Server, and also allows you to save money as compared to buying the tools separately.

Comments are closed.

Your subscription could not be saved. Please try again.
Confirm your email by clicking the link in your inbox!

Subscribe to our blog

to get the latest posts delivered to your inbox