Activity overview
Latest activity by aolcot
I would also like to see this feature added as I often get caught out by this as well. / comments
I would also like to see this feature added as I often get caught out by this as well.
Hi. I think you can do this by using the /export:<directory> (or /e) command line option. / comments
Hi. I think you can do this by using the /export:<directory> (or /e) command line option.
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?
Sorry!. i should have realised with the .sdc file extension that you referred to.
you can still get the options from the command line using:
SQLDataCompare.exe /?
or
SQLDataCompare.exe /v /?
Here is an example command line with data compare that we used to use to sync the data. I did find it initially a bit fiddly to get working, hence the extra options. You may not need these depending on your schema.
.\sqldatacompare /scr1:"C:\CI\Sql Server\Databases\Production" /s2:SqlSvr /DB2:MyDb /sync /o:d /o:fc /o:t /o:k /f
You could use a project file and specify the name of it with the /pr option e.g. sqldatacompare /pr:"myproject.sdc", but I've never done that and elected to do it all through the options available in the command line.
the critical parameter is the /sync option which is what forces it to perform the update.
hope this helps. / comments
Sorry!. i should have realised with the .sdc file extension that you referred to.
you can still get the options from the command line using:
SQLDataCompare.exe /?
or
SQLDataCompare.exe /v /?
Here i...
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.
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.