- or
6 results found
-
Ability to safely edit the previous server lists
Please see this thread
https://forum.red-gate.com/discussion/comment/162865#Comment_162865
I would suggest that because the proposed solution requires knowledge and access to the Registry this should be a feature to edit the list.
7 votes -
Add Summary Details to Script
It would be helpful if the comment header of scripts generated by SQL Compare included the list of Actions present in the Summary tab of the Deployment dialog box.
We keep copies of all Production deployment scripts, but without scanning through the entire script, it can be hard to identify what is going on in each script. Having an option to include that data in the comment header would make it easier for us to track down and review what changes went out with what release.
3 votes -
BUG: SQL Difference pane shows non-existing differences in preview bar
The preview bar on the left of SQL Difference pane shows dark blue segments for the lines that have no actual difference at all. It also appears that it is showing them for the comment lines generated by the tool, like -- Columns and -- Permissions. Version 12.0.30.3199 Professional
1 voteWe think we’ve fixed this bug in the latest Frequent Update release, version 12.0.34. Does this solve your problem?
-
Allow comparing objects of all types with different names, not just tables.
It would be nice to be able to use RGSC to compare such objects by re-mapping. A recent change allows doing this, but with tables only. All other objects would be a helpful touch.
This could be useful for several scenarios, including demonstrating a proposed change to a current version. We also sometimes end up with different test versions of objects that differ slightly with less than helpful comments. (b/c all our devs' code is self documenting!)45 votes -
Commented-out blocks of code should show as changed
When an entire block of code is commented out with the /* */ characters, SQL Compare only shows only the lines with these characters as changed. It does not show the unchanged block of code between them as changed, even though the impact of commenting out this code can indeed be a significant change.
I suggest that unchanged lines of code enclosed by /* */ around it should still show as a substantive change. When we recently deployed an SP update with a large block of code that was commented out during testing, it slipped in because…
1 vote -
Script Generation: Control over the sp_rename of a table
When you add a non nullable column in a table, there is a warning that the script can fail. The generated script will issue will try to help by removing all contraints, rename the table and recreate it. This cannot be done on large table (with data). The only choice I have is to add the column as nullable, add the initialisation in the script and make it not null after. So, I would like to accept the warning and to let the 'alter table add column' been generated with a comment in the generated script. I guess to work…
1 vote
- Don't see your idea?