Comments
Sort by recent activity
Scott,
SQL Compare should only use a temporary table to rebuild a table when a change cannot be made via an ALTER statement.
Situations where we use rebuilds are:
make change an identity value
add a column in the middle of a table when force column order is enabled
add/alter/drop PERSISTED computed columns
when it is not possible to cast one data type to another implicitly
change filegroups
change partitioned columns
We have to use a temporary table is the only way to ensure that data is persisted. If SQL Compare is using temporary tables in a situation where an ALTER can be used then we have an issue which we should fix.
We may be able to make changes to SQL Compare in the future to ensure that it can switch the replication to the new table.
Hope this explains our thinking on this matter,
Regards,
Jonathan / comments
Scott,
SQL Compare should only use a temporary table to rebuild a table when a change cannot be made via an ALTER statement.
Situations where we use rebuilds are:
make change an identity value
add...
Moved to the correct forum.
Regards,
Jonathan / comments
Moved to the correct forum.
Regards,
Jonathan
I think you are refering to SDC 6 Alpha, so I have moved this topic to the correct forum. / comments
I think you are refering to SDC 6 Alpha, so I have moved this topic to the correct forum.
We have added a fix for sp_renamed objects in SQL Compare 6. So this should help you out.
Regards,
Jonathan / comments
We have added a fix for sp_renamed objects in SQL Compare 6. So this should help you out.
Regards,
Jonathan
Hi there,
Perhaps we should be doing some extra checking of tables, in the same what that SSMS does, this would then get around the problem. I will raise an issue for this to be fixed in a future version of SC.
Regards,
Jonathan / comments
Hi there,
Perhaps we should be doing some extra checking of tables, in the same what that SSMS does, this would then get around the problem. I will raise an issue for this to be fixed in a future ...
Hi there,
Unfortunately the reporting code is loacted in user interface which isn't part of the Toolkit license. So if you want to use the toolkit to generate reports, the only way to do it is to read the results and generate a report by hand.
I know this isn't ideal so have raised a request to get this moved from the private UI code to the public API.
However, if you are already using a batch file, then perhaps using the SQL Compare command line would be your best bet. You can do pretty much everything that you can do with the toolkit, plus it does also allow you to gain access to the html reports that are in the UI.
Hope this helps,
Regards,
Jonathan / comments
Hi there,
Unfortunately the reporting code is loacted in user interface which isn't part of the Toolkit license. So if you want to use the toolkit to generate reports, the only way to do it is to ...
Hi there,
I have answered your query in your post on the SQL Compare v6 forum here: http://www.red-gate.com/MessageBoard/vi ... 9395#19395.
Thanks,
Jonathan / comments
Hi there,
I have answered your query in your post on the SQL Compare v6 forum here: http://www.red-gate.com/MessageBoard/vi ... 9395#19395.
Thanks,
Jonathan
Hi there,
We are working on implementing this feature at the moment it should be in version 6.1, the release date for this hasn't been confirmed just yet. But it should be sometime in the next month or two.
Regards,
Jonathan / comments
Hi there,
We are working on implementing this feature at the moment it should be in version 6.1, the release date for this hasn't been confirmed just yet. But it should be sometime in the next mont...
Hi there,
Sorry, no this isn't possible in the current UI. Whilst we could reorder the columns in the SQL Differences pane, it wouldn't be a true representation of what the databases looked like so we have always shied away from doing it.
We are seriously thinking of ways that we can improve the difference matching and hope to get this into a future version of the product.
Regards,
Jonathan / comments
Hi there,
Sorry, no this isn't possible in the current UI. Whilst we could reorder the columns in the SQL Differences pane, it wouldn't be a true representation of what the databases looked like s...
Hi there,
Okay, I can see the problem, you have a numbered stored procedure.
Unfortunately this is a limitation within the SQL Compare engine, whilst SQL Compare can compare numbered stored procedures the execution of scripts containing them fails as the execution block cannot contain a GO batch delimiter which between the two parts of the stored procedure.
Currently the only workaround is to execute the script manually.
Regards,
Jonathan / comments
Hi there,
Okay, I can see the problem, you have a numbered stored procedure.
Unfortunately this is a limitation within the SQL Compare engine, whilst SQL Compare can compare numbered stored procedu...