Red Gate forums :: View topic - How to Exclude Assembly in SQL Compare Pro Command-Line?
Return to www.red-gate.com RSS Feed Available

Search  | Usergroups |  Profile |  Messages |  Log in  Register 
Go to product documentation
SQL Compare 10
SQL Compare 10 forum

How to Exclude Assembly in SQL Compare Pro Command-Line?

Search in SQL Compare 10 forum
Post new topic   Reply to topic
Jump to:  
Author Message
MrSuaveh



Joined: 07 Jul 2014
Posts: 1

PostPosted: Mon Jul 07, 2014 7:52 pm    Post subject: How to Exclude Assembly in SQL Compare Pro Command-Line? Reply with quote

I am using SQL Compare Pro 10.4.8 and have tried using
    /Exclude:Assembly
    /Exclude:Assembly:sersolsharedcode
    /Exclude:Assembly AND /Exclude:Assembly:sersolsharedcode

However SQL Compare Pro keeps failing with the error message:
Code:
Error: Synchronization of 'DBMSSQL2.Devqa.sersol.il.pqe\COREDB3.LibraryDB' and '87P7WK1.Devqa.sersol.il.pqe,1433.LibraryDB' failed: Assembly 'sersolsharedcode,
version=1.0.0.0, culture=neutral, publickeytoken=221f68f4f5ae01e4.' was not found in the SQL catalog.

How can I prevent SQL Compare Pro from attempting to synchronize CLR spocs? I can do it interactively but not through the command line.

This is the SQL Compare Pro command I am using:
Code:
sqlcompare
/server1:DBMSSQL2.Devqa.sersol.il.pqe\COREDB3 /DB1:LibraryDB
/server2:87P7WK1.Devqa.sersol.il.pqe,1433 /DB2:LibraryDB 
/Synchronize /Force
/Report:"F:\My Documents\DEV\CCM\databases\SandBox\RickJones\SQLCompare\SQLCompareReports\DBMSSSQL2_87P7WK1_Synch_LibraryDB.html"
/reportType:Simple /logLevel:Verbose
/Exclude:Certificate /Exclude:Assembly /Exclude:Assembly:sersolsharedcode
/Exclude:Identical /Exclude:view:viewCoreLibraryDatabaseWithCodes
/Exclude:storedprocedure:prcUlrichsWebFeedRefresh2 /Exclude:view:viewCounterOutJournal


Thanks,
Rick
Back to top
View user's profile Send private message
Admin
Site Admin


Joined: 15 Aug 2004
Posts: 9

PostPosted: Thu Jul 10, 2014 2:48 pm    Post subject: Reply with quote

Hi Rick,

If I understand correctly, this error is probably happening because the assembly has been excluded. Then you would get this error if an object that depends on that assembly (such as a stored procedure or user-defined function) was being applied to the database without the underlying assembly.
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Reply to topic All times are GMT + 1 Hour
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group