How can we help you today? How can we help you today?
JonathanWatts
The default options cannot be changed. We may change this in future versions, but at the current time Tom's workaround is the only way to do this. Regards, Jonathan / comments
The default options cannot be changed. We may change this in future versions, but at the current time Tom's workaround is the only way to do this. Regards, Jonathan
0 votes
Great! Thank you for checking that. I will take another look at the installer shortly. Regards, Jonathan / comments
Great! Thank you for checking that. I will take another look at the installer shortly. Regards, Jonathan
0 votes
Hi there, I can I just double check the build you are using? As RC1 for SQL Compare should be 5.0.0.1559. Thanks, Jonathan / comments
Hi there, I can I just double check the build you are using? As RC1 for SQL Compare should be 5.0.0.1559. Thanks, Jonathan
0 votes
Hi there, We haved posted the RC1 which should have fixed this issue, if you could give it a try again it would be very appreciated. Thanks, Jonathan / comments
Hi there, We haved posted the RC1 which should have fixed this issue, if you could give it a try again it would be very appreciated. Thanks, Jonathan
0 votes
Hi Oleg, This sounds like an issue we are investigating. Is the white space problem one new line at the end of an object on a SQL2005 database? Regards, Jonathan / comments
Hi Oleg, This sounds like an issue we are investigating. Is the white space problem one new line at the end of an object on a SQL2005 database? Regards, Jonathan
0 votes
Yes that would be the reason, SQL Data Compare cannot currently compare tables in different schema. You are also correct in saying that schemas are now object owners rather than the user. Regards, Jonathan / comments
Yes that would be the reason, SQL Data Compare cannot currently compare tables in different schema. You are also correct in saying that schemas are now object owners rather than the user. Regards, ...
0 votes