dbForge Schema Comparer 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-2008, it could be CREATE TYPE dbo.[State] FROM bit NOT NULL.
Different syntax:
But how about some data types and objects appeared in latter 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.
Inconsistent Object:
Some objects, mainly containing custom code, such as stored procedures and functions, may have incompatibility in their syntax. This will required 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 analyze your databases for these conditions before synchronization.
No comments:
Post a Comment