HELP! SC8 not respecting the database compatibility mode
Our database is set to compatibility mode 8.0 (2000) because many of our clients are still running SQL 2000. I used to have my live and staging databases running in SQL 2000. SQL Compare 7 (and then 8 ) always worked great for creating version update scripts for all clients, regardless if they were running SQL2000, 2005 or 2008.
Last month, I just upgraded my PC to Win7 (x64), so I could no longer run SQL 2000. I therefore moved my staging and live databases to SQL 2005, but kept the compatibility mode of both databases set to 8.0. On the last version update script I made with SC8 and deployed to our clients, all of them still on SQL 2000 get "For DROP INDEX, you must give both the table and the index name, in the form tablename.indexname" and other syntax errors.
The only workaround I can see is to install and run SQL 2000 inside Windows Virtual PC just to create these SQL Compare scripts that will work for our SQL 2000 clients. Please say this isn't so. You guys REALLY NEED to change SQL Compare to respect the compatibility mode setting of at least the target database.
In the meantime, is there anything I can do? Right now, I and my SQL 2000 clients are screwed. Thanks.