Comments
2 comments
-
A standard sync will theoretically have the same effect (making the target DB match the source). This is the same as clearing down everything from the target then syncing. So I think I'm perhaps missing the point of what you're trying to do.
There's no option in SQL Compare to do this; but a workaround would be to have an empty database on your server, and first sync from this to the target (which should drop everything) then run your usual sync afterwards. But as I said above, the end result would be the same as the sync you're already doing. -
Are you running this as part of an automated process? If so, an alternative is to run the following:
sqlcmd -SYourServer -Q "ALTER DATABASE YourDB SET SINGLE_USER WITH ROLLBACK IMMEDIATE; DROP DATABASE YourDB"
sqlcmd -SYourServer -Q "CREATE DATABASE YourDB"
Can I ask why you're creating these schema backups? How will they be used?
David Atkinson
Product Manager
Red Gate
Add comment
Please sign in to leave a comment.
I know this process might be a bit weird but what we're trying to do here is to create a schema backup for multiple databases by using redgate to sync with a staging DB before creating a backup of it.
thanks,
brian