Comments
Sort by recent activity
hi. Yes this is all perfectly possible by executing SQLCompare.exe from the command line which you could wrap within powershell or a multitude of other tools... You could wrap it up within a console app, but it would be better within powershell i feel.
To find out the options that SQLCompare offers you could run the following:
sqlcompare /?
or to get more verbose information:
sqlcompare /v /?
Here is some more information regarding the use of the command line. http://www.red-gate.com/supportcenter/List?t=API_CommandLine&p=SQL%20Compare
Example usage from our CI. This syncs a database from a scripts folder which could just as easily be a database instead:
sqlcompare /scr1:"C:\CI\Sql Server\Databases\Development" /s2:SQLSvr /DB2:MyDb /exclude:role /exclude:user /o:n /q /f /sync
Hope this helps / comments
hi. Yes this is all perfectly possible by executing SQLCompare.exe from the command line which you could wrap within powershell or a multitude of other tools... You could wrap it up within a consol...
Hi thu,
You can use the parameters /s1 and /s2 to point to different instances e.g.
SQLCOMPARE /s1:mysqlserver\instance1 /s2:mysqlserver\instance2 /db1:mydb1 /db2:mydb2
Hope this helps. / comments
Hi thu,
You can use the parameters /s1 and /s2 to point to different instances e.g.
SQLCOMPARE /s1:mysqlserver\instance1 /s2:mysqlserver\instance2 /db1:mydb1 /db2:mydb2
Hope this helps.
hi thu, Can you provide the full command line that you are using during the compare process please? / comments
hi thu, Can you provide the full command line that you are using during the compare process please?
Exit code 64 from SQL compare means "General command-line usage error"
Now looking at the error, I think SSIS has specified the entire command line within double quotes. Could that be linked to the problem? / comments
Exit code 64 from SQL compare means "General command-line usage error"
Now looking at the error, I think SSIS has specified the entire command line within double quotes. Could that be linked to the...
Unfortunately, I'm not aware that it is currently possible using SQL Compare to ignore database references that are in the definition of a view.
Going forward, converting your hard coded database references to synonyms may be a potential solution. / comments
Unfortunately, I'm not aware that it is currently possible using SQL Compare to ignore database references that are in the definition of a view.
Going forward, converting your hard coded database r...
You can compare two databases on the same SQL instance from the project options. Can you clarify exactly where you need to ignore the database name? Do you have hard coded database name references in your procedures/triggers for example that you are trying to ignore?
Synonyms are a useful feature to allow you to use an alternative name for a database object that is could be local or remote. Or, as we use them, a means to reference an object in a different database on the same SQL instance without specifying a hard database name within the procedure or trigger. / comments
You can compare two databases on the same SQL instance from the project options. Can you clarify exactly where you need to ignore the database name? Do you have hard coded database name references ...
Unless I have misunderstood your question, but wouldn't you want to version control the data within the base tables instead seeing as a view is just something referencing those base tables. / comments
Unless I have misunderstood your question, but wouldn't you want to version control the data within the base tables instead seeing as a view is just something referencing those base tables.
Nice one James! That has helped me out as well as I did find using profiler without setting a filter a touch more annoying as all the events were from SSC.
It would be nice to make this "easier" to configure from within the GUI though as I'm sure many others would want to fine tune/disable polling. / comments
Nice one James! That has helped me out as well as I did find using profiler without setting a filter a touch more annoying as all the events were from SSC.
It would be nice to make this "easier" to...
My experience with SSC is that it is fantastic at helping to source control the schema, but as of yet, not so good with the data. I have found that if you want to source control some data from a table, then unless there are a relatively few number of records then SSC suffers from performance issues. And when I say a "few records" a few means in the 100's absolute maximum.
It is one thing to get the data sync'd into an empty database, but when trying to detect changes before a commit to source control, a significant amount of data does cause SSC to spend a lot of time working out the data differences.
It got so bad for us with our platform that we decided to take out data from source control until a future time that SSC can handle data much more effectively. We run the data in as a post build script manual task and I hear on the grapevine that the next version of SSC may have support for these type of pre/post build scripts which would be great!...
Sorry to not to be able to offer a solution. Just wanted to share our experiences and would be keen to find out if there are workarounds to speed up the data sync process in SSC. / comments
My experience with SSC is that it is fantastic at helping to source control the schema, but as of yet, not so good with the data. I have found that if you want to source control some data from a ta...
I believe that this exit error is raised when everything is identical, but it can be suppressed by using the /include:identical setting / comments
I believe that this exit error is raised when everything is identical, but it can be suppressed by using the /include:identical setting