Comments
5 comments
-
Are you referencing linked servers?
If so, this is a known issue, and we have an existing enhancement request to provide an option for setting the transaction isolation level to use in your scripts (ref. SC-1318) -
Yes, we're using linked servers. Is there a timeframe for that feature to get added? I need to decide whether it is worth waiting or if I should implement another solution.
-
Unfortunately, I'm not sure precisely when this will be implemented - it's currently marked as 9.x and quite a few people have asked for it, so hopefully it shouldn't be too long. I've added a note of this thread to the job to give it another "vote" in any case.
-
Much appreciated, thanks!
-
The isolation level can now be configured in the application.
Please visit http://www.red-gate.com/MessageBoard/vi ... 1312#51312 for more information.
David Atkinson
Product Manager
Red Gate Software
Add comment
Please sign in to leave a comment.
I can't get the synchronization wizard to work at all. First I was getting the error: "MSDTC on server 'blah' is unavailable". So I went into services and enabled the Distributed Transaction Coordinator service, and now I always get the error "Transaction context in use by another session."
The only way that I've found to get around this is to modify the script by hand and change the isolation level to READ COMMITTED. Eventually I plan on using this tool to automate our database deployments so I need to get it working without manual intervention. Is there a configuration option somewhere that I can change to fix this problem? Thanks.
This error was present in the previous version also (8.5).