i think that SQL Compare should not auto save the sync script if the sync faild. i try running a sync from sql 2005 to sql 2000 and some times it fails because of competability problems. when that happens the db sync fails and i still end up with a useless script saved
Comments
3 comments
-
Hi Dan,
Wouldn't it actually be even more useful to have a copy of the script in that case to try to diagnose the cause of the failure? -
when the sync fails the error is displayed. usually it involves using non deterministic functions which are allowed on sql 2005 but not on 2000. i see the error and fix it. then i refresh the comparison and try running the sync again. until the run is successfull i have to do this a few times and i end up with 10 scripts which only the last one passes and the rest fail at some point. maybe you should add this as an option to sql compare to delete the script if the sync fails.
-
Hello Dan,
SQL Compare 5.2 now has an extra 'save script' option in the synchronization wizard.
Add comment
Please sign in to leave a comment.