Activity overview
Latest activity by pellben
In the same way, when we use that command (we've removed /INCLUDE:Trigger option),
"SQLCompare.exe" /scripts1:"%DBScriptsPath%" /s2:"%SqlServer%" /db2:"%BName%" /include:View /include:Function /include:StoredProcedure /allowIdenticalDatabases /synchronize"
We have that error message
Registering databases
Unexpected error: Failed to locate the CLR assembly xxxx.yyy.CLR_Extensions for
the [dcs].[EvalCondition] stored procedure.
Failed to locate the CLR assembly xxxx.yyy.CLR_Extensions for the [yyy].[EvalCondition] stored procedure.
RedGate.SQLCompare.Engine.SqlCompareException
at RedGate.SQLCompare.CommandLine.CommandProcessor.d()
at RedGate.SQLCompare.CommandLine.CommandProcessor.e()
at RedGate.SQLCompare.CommandLine.CommandProcessor.Run()
at RedGate.SQLCompare.CommandLine.Startup.a(String[] )
Error occured while executing SQLCompare. SQLCompare aborted.
But the assembly exist on destination database. It was created before in Migration scripts. When we use SQL Compare 7 GUI , that will run, we can create SP's. / comments
In the same way, when we use that command (we've removed /INCLUDE:Trigger option),
"SQLCompare.exe" /scripts1:"%DBScriptsPath%" /s2:"%SqlServer%" /db2:"%BName%" /include:View /include:Function /in...
We refering to DML Triggers / comments
We refering to DML Triggers
We don't included tables in the comparison (since handled by our migration scripts) but the /include:trigger option set. Our triggers were always synchronized with v6. I don't think this option is ignored in v6.
Is there a way to do this with version v7?
You have to know that we are using a build server and SqlCompare.exe. We compare against source control files and a destination database, not against a source database. We are treating triggers as source code, just like stored proc, but not tables. Tables are NOT synchronized with SqlCompare.exe but by migration scripts. / comments
We don't included tables in the comparison (since handled by our migration scripts) but the /include:trigger option set. Our triggers were always synchronized with v6. I don't think this option is ...
Thanks
but we are using migration scripts (SQLCMD) to deploy table changes and using SQLCompare to synchronize our Stored Procs, Functions, Views and Triggers, which come from source controlled files (database code objects). We do this using a build server.
So, what you are saying is that the new SQLCompare 7 is no longer supports Trigger ??? Trigger were successfully synchronized with version 6. Is there a workaround? Or can we get this feature back? For now, we will have to revert to version 6.
Regards, / comments
Thanks
but we are using migration scripts (SQLCMD) to deploy table changes and using SQLCompare to synchronize our Stored Procs, Functions, Views and Triggers, which come from source controlled fil...
SQL Compare 7 /Include:Trigger option
We've used SQL Compare 6 when we deploy form VS Studio and everything running well, now we upgrade SQL Compare 7 and we got this Error Message
Invalid value for switch /include: Trigger. Please us...