Sql Compare 6 produces script not working on SQL 2000

• 
  Compare actually determines which syntax to use based on the target database's version, so if you can get a database snapshot from an empty SQL Server 2000 database (I can email you one if necessary), you can compare against that and use the resulting script.

  Michelle T December 18, 2007 10:01

  - 0 +
• 
  I don't really understand. My situation is:
  
  I have a 2005 database backup (development database with table changes).
  I have a 2000 database backup (customer database that should become the same as the development database but customer has sql 2000)
  I have a development computer with Sql Server 2005 and Sql compare 6 and both database are mounted.
  
  What should i do to create a 2000 compatible update script for our customer? Thanks in advance.

  RaymondKurzweil December 18, 2007 15:39

  - 0 +
• 
  Ah. The problem is that there's currently no way to tell SQL Compare to generate a 2000 compatible upgrade script other than having the target database be a SQL Server 2000 database.
  
  You can work around it if you have SQL Compare Pro:
  
  1) Save the 2000 database to scripts
  2) Register the resulting scripts folder as a SQL Server 2000 database and save it as a snapshot
  3) Compare your 2005 database against the snapshot
  
  I've added a feature request to our bug database for the feature 'select which version of SQL Server the synchronization script should target, independant of the actual target version' - is that correct?

  Michelle T December 19, 2007 06:15

  - 0 +
• 
  Unfortunately, we don't have the pro edition.
  
  That feature request sounds correct. Thanks.

  RaymondKurzweil December 20, 2007 04:13

  - 0 +

Add comment

Please sign in to leave a comment.