Comments
Sort by recent activity
You can also work around this without having a SQL 2000 server at all:
1) Create a script folder of your target database
2) In the edit project dialogue, set the SQL Server version of the script folder to SQL Server 2000
2) Compare to the script folder
3) Choose to generate a synchronization script in the sync wizard
This should fool SQL Compare into believing it's synching to a SQL 2000 server and hence make it generate the right syntax. / comments
You can also work around this without having a SQL 2000 server at all:
1) Create a script folder of your target database
2) In the edit project dialogue, set the SQL Server version of the script fo...
You'll need to email sales@red-gate.com and ask them to sort out the licensing for you - if you've ever had a standard edition of a product installed, it won't automatically give you a trial license for the professional edition. / comments
You'll need to email sales@red-gate.com and ask them to sort out the licensing for you - if you've ever had a standard edition of a product installed, it won't automatically give you a trial licens...
Ah, looks like a terminology problem then [image] .
SQL Compare's include / exclude dependencies option refers to dependencies _within_ the same database - when you've selected only some of the objects in a database to be synchronized, but some of your selected objects depend on other objects, SQL Compare will include those objects if you have IncludeDependencies on, and won't if you have removed it.
So on the command line, it's only useful when combined with the /include: and/or /exclude: switches.
It looks like the problem you're having is a SQL Server problem - you can't recreate / alter some objects which reference other objects that are no longer accessible. As far as I know, there isn't an easy way around this - SQL Server checks at the time you create an object if the objects referenced by that object exist, and refuses to create (or alter) the object if they don't.
Sorry for the confusion, and I hope that has at least cleared it up, even though it looks like we can't help with the actual problem... / comments
Ah, looks like a terminology problem then .
SQL Compare's include / exclude dependencies option refers to dependencies _within_ the same database - when you've selected only some of the objects in ...
To exclude dependencies you have to specify the /Options: switch, overriding the default options.
You can just specify /Options:none to exclude dependencies, but you may want to add back in the other default options:
/Options:DecryptPost2KEncryptedObjects,IgnoreFillFactor,IgnoreWhiteSpace,IgnoreFileGroups,IgnoreUserProperties,IgnoreWithElementOrder
Does that help? / comments
To exclude dependencies you have to specify the /Options: switch, overriding the default options.
You can just specify /Options:none to exclude dependencies, but you may want to add back in the oth...
When you save a script folder, SQL Compare also saves some information about that script folder (including the encoding) in an XML file - RedGateDatabaseInfo.xml.
Generally we recommend that you save another script folder with the right settings instead of manually modifying the XML file, but if that's not possible then you can try changing the value of the 'ScriptFileEncoding' element to 'Windows1252' with a text editor.
Then SQL Compare may stop trying to read the files as pure ASCII and start trying to read them as Windows-1252, which will probably work if that's what they are actually currently in.
Obviously we don't usually recommend this and can't be certain that it won't cause other problems, but it might help in your situation. / comments
When you save a script folder, SQL Compare also saves some information about that script folder (including the encoding) in an XML file - RedGateDatabaseInfo.xml.
Generally we recommend that you sa...
If you're saving script folders (as opposed to synchronization scripts) you may be able to work around your problem by saving in Windows-1252 instead of ASCII. Most Windows programs like Notepad which are displaying £ symbols and saving in 'ASCII' are actually saving in Windows-1252 anyway - it's just a particular ANSI code page.
Unfortunately we haven't got the option to save synchronization scripts in Windows-1252 yet - if you'd find this useful, we could add a feature request to the list to get this added to the options. / comments
If you're saving script folders (as opposed to synchronization scripts) you may be able to work around your problem by saving in Windows-1252 instead of ASCII. Most Windows programs like Notepad wh...
If there are no 2008-specific data types or features involved, you should just be able to compare the 2008 backup to a 2005 database.
To restore to a server that doesn't have a comparable database, you will first need to create an empty database with the required filegroups etc, then use SQL Compare to synchronize the schema into the database. After that you can use SQL Data Compare to synchronize the data across.
Does that answer your question? / comments
If there are no 2008-specific data types or features involved, you should just be able to compare the 2008 backup to a 2005 database.
To restore to a server that doesn't have a comparable database,...
Could you tell us what went wrong? Was it that there were 2008-specific features, server-level differences (which would have manifested as problems synchronizing users) or some other issue?
While the tools aren't specifically designed as downgrade tools, it's good to know what problems people face in this area so we can improve our offering... / comments
Could you tell us what went wrong? Was it that there were 2008-specific features, server-level differences (which would have manifested as problems synchronizing users) or some other issue?
While t...
Yes - in the Tables & Views tab of the Project Configuration dialog, find the table with the column you want to ignore, and access the drop-down on the column headed 'Columns'. Then uncheck the box of the column you want to ignore.
Does that solve your problem? / comments
Yes - in the Tables & Views tab of the Project Configuration dialog, find the table with the column you want to ignore, and access the drop-down on the column headed 'Columns'. Then uncheck the box...
You might find that SQL Compare produces less refreshview statements if you create the script through the GUI (or if you need to use the command line, create a project in the GUI, save the project, and use the /pr: switch on the command line to use the project to generate the script).
The extra view refreshes are a known issue (SC-4542) which we'll hopefully get fixed soon. / comments
You might find that SQL Compare produces less refreshview statements if you create the script through the GUI (or if you need to use the command line, create a project in the GUI, save the project,...