Comments
Sort by recent activity
Also, to answer your question; it will not be possible to send DB snapshots in this case due to sensitive data. / comments
Also, to answer your question; it will not be possible to send DB snapshots in this case due to sensitive data.
I had a similar situation and came up with a workaround.
On the first step of my sync job, I execute the following: use destination_database
go
create table fake_table_for_redgate
(
fake_column int )
go
That way when the sync runs, it will always find a destination table that doesn't have a matching source table and then drop the table. Obviously not the ideal way to do things, but it works. / comments
I had a similar situation and came up with a workaround.
On the first step of my sync job, I execute the following:use destination_database
go
create table fake_table_for_redgate
(
fake_column ...
Hmm... I'll dig a little deeper then, perhaps the statement I was able to execute manually wasen't the same one that generates the error message. / comments
Hmm... I'll dig a little deeper then, perhaps the statement I was able to execute manually wasen't the same one that generates the error message.
The databases I'm comparing have many thousands of objects. Is there a way to get a more descriptive error message, ie. something that tells me which statement caused the error? / comments
The databases I'm comparing have many thousands of objects. Is there a way to get a more descriptive error message, ie. something that tells me which statement caused the error?
Nevermind, I generated a SQL Script for all the changes and can see where the problems are. You're correct, it's a SQL Server message, not a SQL Compare message.
Thanks. / comments
Nevermind, I generated a SQL Script for all the changes and can see where the problems are. You're correct, it's a SQL Server message, not a SQL Compare message.
Thanks.
Ah, that works much better.
So, to clarify, in SDC 7 the command line syntax for selecting specific tables was: /include:table:\[table1\]^|\[table2\]^|\[table3\]
Whereas in SDC8, the following syntax is correct? /include:table:^table1$^|^table2$^|^table3$
That seems confusing to me...
Also, your online documentation seems to indicate that the square bracket syntax is correct, not the $ syntax you posted, and probably needs to be updated. / comments
Ah, that works much better.
So, to clarify, in SDC 7 the command line syntax for selecting specific tables was:/include:table:\[table1\]^|\[table2\]^|\[table3\]
Whereas in...
Quick update: I installed the latest cumulative patch for SDC 8 to see if it would help, now I'm getting a different error: E:\>"E:\Red Gate\SQL Data Compare 8\SQLDataCompare.exe" /verbose /server1:the_real_prodc /server2:ladbmo01\lamo
m /database1:pricing /database2:pricing /include:table:\[tbl_ppws_cfg_maint_expense\]
Red Gate SQL Data Compare Command Line Utility V8.0.5.42
==============================================================================
Copyright c Red Gate Software Ltd 1999-2009
Serial Number:
Comparing database the_real_prodc.pricing with database ladbmo01\lamom.pricing...
Registering databases
Mapping
Error: Object reference not set to an instance of an object.
/ comments
Quick update: I installed the latest cumulative patch for SDC 8 to see if it would help, now I'm getting a different error:E:\>"E:\Red Gate\SQL Data Compare 8\SQLDataCompare.exe" /verbose /serve...
The latest update that you posted does not solve the original problem.
It does fix the "Object reference not set to an instance of an object." error, but the "The selected objects are identical or no objects have been selected in the comparison." error remains. / comments
The latest update that you posted does not solve the original problem.
It does fix the "Object reference not set to an instance of an object." error, but the "The selected objects are identical or ...