Activity overview
Latest activity by bveenstra
"no plumbing" I believe is a reference to a command-line option... what you're looking for is to turn on "Do not use transactions in synchronization scripts" ... it feels like a double-negative, does it not? [image] / comments
"no plumbing" I believe is a reference to a command-line option... what you're looking for is to turn on "Do not use transactions in synchronization scripts" ... it feels like a double-negative, do...
Andras wrote:
So you need to include:
SET TRANSACTION ISOLATION LEVEL REPEATABLE READ
Unfortunately that did not work for our 2005 environment either.
Isn't there any way for SQLCompare to "test" this workaround for Linked Servers during startup/new project?
Andras wrote:
Another alternative is that if you are confident that the transaction will succeed, and there are no strange dependency problems, you may use the NoPlumbing option in SQL Compare's options. Note, that when this option is selected, the synchronization is not executed in a transaction, thus rollback does not work.
Could you make a distinct option for SQLCompare to use Transactions where it can, and exclude transactions on items containing Linked Servers? That would be the most elegant solution in my mind. Perhaps different color coding on the Compare results grid? / comments
Andras wrote:
So you need to include:
SET TRANSACTION ISOLATION LEVEL REPEATABLE READ
Unfortunately that did not work for our 2005 environment either.
Isn't there any way for SQLCompare to "te...