Search
-
Re: SQL Compare bad transaction management
In case my explanation above does not make sense, here is a clarification based on a simplified case of a single SVN checkin. If I attempt to add a Migration Script to this check in, the following code is generated for me (note that I have removed a lot of lines to make my case more clear to the reader). EXEC… -
Re: SQL Compare bad transaction management
Anything new on this subject? Since a bug has been logged, does this mean that Migration Script SHOULD have been padded with the be padded with the code below after every command? IF @@ERROR<>0 AND @@TRANCOUNT>0 ROLLBACK TRANSACTION GO IF @@TRANCOUNT=0 BEGIN INSERT INTO #tmpErrors (Error) SELECT 1 BEGIN TRANSACTION END GO -
SQL Compare bad transaction management
Hi, I am having a problem making SQL Compare generate usable script (with a functional transaction roll back mechanism) when using Migration Scripts. We often use SQL Compare to generate DB script to be run on our customer's databases. If the intermediary SVN checkin(s) contain only auto generated code (i.e. no migration…
3 results