Comments
Sort by recent activity
Hi,
I think there was a bug in version 6.0 of the command line that meant your GUI table selections weren't honoured by the command line, but other settings (correctly) were. This has been fixed, and will be in the 6.1 release of Data Compare (due early Q1 2008).
For now, if you just want to compare one table, you can use the /include switch in addition to the /project switch:
sqldatacompare.exe /project:"MyProject.sdc" /include:MyTable
If it appears to still hang, I wonder if you could check the CPU usage of Data Compare to see if it's really doing anything or not. It might also be worth checking you haven't got an evaluation screen popped up somewhere in the background if you're in the trial period at the moment.
Hope that helps,
Robert / comments
Hi,
I think there was a bug in version 6.0 of the command line that meant your GUI table selections weren't honoured by the command line, but other settings (correctly) were. This has been fixed, a...
Hi,
The "disable foreign keys" option only disables them temporarily during the insert / update / delete operations - it doesn't leave them disabled afterwards. This means if you're synchronizing a table that has dependencies on tables you're not synchronizing, you can end up with errors.
This is the same behaviour as if you try and synchronize using the GUI.
Robert / comments
Hi,
The "disable foreign keys" option only disables them temporarily during the insert / update / delete operations - it doesn't leave them disabled afterwards. This means if you're synchronizing a...
Hi,
There's two ways of setting a WHERE clause, depending on how you're running Data Compare.
If you're using the .NET API, then you have a Where property (taking a WhereClause object) on the TableMapping. Obviously you can set this as flexibly as you like.
If you're using the Data Compare command line, you can't set a WHERE clause directly, but you can specify a project created using the graphical interface, which does allow you to set these. This should work if you're always wanting to use the same WHERE clause for each run, but maybe not if you need to dynamically generate it.
I hope that helps - if you've got any questions, please let me know.
Regards,
Robert / comments
Hi,
There's two ways of setting a WHERE clause, depending on how you're running Data Compare.
If you're using the .NET API, then you have a Where property (taking a WhereClause object) on the Table...
No worries - glad it's useful to you! / comments
No worries - glad it's useful to you!
Hi,
If you look in the "tables and views" tab of the project configuration dialog, there's a column named "columns in comparison". If you edit this for your tables, and deselect certain columns, they won't be compared or altered.
Hope this helps,
Robert / comments
Hi,
If you look in the "tables and views" tab of the project configuration dialog, there's a column named "columns in comparison". If you edit this for your tables, and deselect certain columns, th...
Hi,
This is probably happening as a result of some schema changes being made to the database. When you select, deselect, remap or similar, that's stored as an "action" in the project. On opening the project, Data Compare attempts to replay these actions.
In version 5 and before, if any of these failed, we restored the default state. In Data Compare 6, we now attempt to keep going as far as possible, so most of the time you'll keep your settings even in the face of schema changes.
Hope that helps,
Robert / comments
Hi,
This is probably happening as a result of some schema changes being made to the database. When you select, deselect, remap or similar, that's stored as an "action" in the project. On opening th...
Hi,
Thanks for the report. I've checked the code, and the point at which it's blowing up is just a call to BindingList.Clear()... so it looks like it could be a bug in the DevExpress grid.
Is this something you've seen multiple times, or was it just a one-off?
Thanks,
Robert / comments
Hi,
Thanks for the report. I've checked the code, and the point at which it's blowing up is just a call to BindingList.Clear()... so it looks like it could be a bug in the DevExpress grid.
Is this ...
Hi,
Just to let you know, 6.1 is now out. You can get this by going to Check for Updates on the Help menu.
Robert / comments
Hi,
Just to let you know, 6.1 is now out. You can get this by going to Check for Updates on the Help menu.
Robert
Hi,
Thanks for the information - that's exactly what I was looking for. The reason it'll appear to keep working in the background is that the crash is actually happening in a background initialisation thread, rather than the UI thread.
Sorry once again for the inconvenience - we'll let you know as soon as we've got a patch available.
Thanks,
Robert / comments
Hi,
Thanks for the information - that's exactly what I was looking for. The reason it'll appear to keep working in the background is that the crash is actually happening in a background initialisat...
Hi,
Bother - I thought that would've cured it. Do you have access to any other database servers that you could run against as the target? (Obviously not actually performing the synchronization!)
Do you get any details regarding the crash, or is it just an instant bail out with no further information?
Sorry this hasn't worked for you so far - and thanks for your help in providing the information!
Robert / comments
Hi,
Bother - I thought that would've cured it. Do you have access to any other database servers that you could run against as the target? (Obviously not actually performing the synchronization!)
Do...