Comments
4 comments
-
Hi there,
Thanks for your post.
The problem is SQL Compare is attempting to alter a table that is part of replication, and the error is being returned from SQL Server.
Essentially, if objects that are used in replication are synchronized, errors may occur. For example, SQL Compare cannot drop a table if it is used for replication.
The only workaround, and I know it's not much of a workaround, is to disable replication before you perform the update. We do have this logged as a feature request, but I don't know when it's likely to be implemented I'm afraid.
Pete -
Out of interest, what version of SQL Server are you using?
David Atkinson
Red Gate Software -
SQL Server 2008. Is it possible to disable replication with the command line or batch file? I'm using this in an integrated build environment and need an autonomous solution...
-
That's a good question. I guess if it can be done in SQL, then sqlcmd.exe could be used?
I'd recommend you post your question on http://ask.sqlservercentral.com/ as this is frequented by many experts in the field.
Add comment
Please sign in to leave a comment.
I tried adding the /Option:NoTransaction but then I get this error:
What is the recommended approach to synchronizing two databases that have replication enabled? If it makes a difference, I'm using the command line.