How can we help you today? How can we help you today?

SQL Compare 10.7 cmd ignoring transactionIsolationLevel

I'm getting differing behaviors between the command-line and GUI versions of SQL Compare 10.7. The GUI is respecting the configured transaction isolation level when it deploys scripts. The command line seems to always use "SERIALIZABLE" regardless of the transactionIsolationLevel flag.

Here's the command line I'm executing:

.\SQLCompare.exe /include="Identical" /include="StaticData" /scripts1="C:\path\to\Scripts" /scriptsfolderxml="C:\path\to\scripts" /migrationsfolder:"C:\path\to\migrations" /server2="(local)" /database2="TestDatabase" /synchronize /AbortOnWarnings="none" /transactionIsolationLevel="READ COMMITTED" /options="default,UseMigrationsV2" /scriptfile="C:\Users\me\Desktop\migration.sql" /force

In the generated script file, there's this:

'SET TRANSACTION ISOLATION LEVEL SERIALIZABLE'

When I do the equivalent operation using the GUI, the script correctly contains 'SET TRANSACTION ISOLATION LEVEL READ COMMITTED'

Any ideas? This is a major roadblock for my team and our use of SQL Compare/Source Control since our scripts involve linked servers and won't work with SERIALIZABLE.

I'm using SQL Compare Command Line V10.7.0.18...
matthoneycutt
0

Comments

3 comments

Sort by
  • Anu D
    Thanks for your post.

    We have logged a support ticket for you and will reply shortly!
    Anu D
    0
  • Anu D
    Thanks for your patience.

    I was able to replicate the issue and hence have logged this in our internal tracking system whose tracking id is SC-7172.

    We will keep you updated on the progress of this issue and also about our plans to fix this.
    Anu D
    0
  • VenkatM
    Was this issue ever fixed? Is there a way to track SC-7172 ?
    VenkatM
    0

Add comment

Please sign in to leave a comment.