254 results found
-
Allow SQL Compare to ignore difference due to ALTER and CREATE
When comparing a VS 2012 database project to a database, when the only difference is ALTER vs. CREATE (which happens because a stored procedure ALTER was executed directly, then saved) the comparison fails. An option to ignore this difference would be very handy.
9 votes -
Fix the installer. Could not install SQL Tool belt trial as Redgate Client service could not be stopped.
I tried to install the SQL Tool belt trial numerous times but was blocked each time saying the Redgate Client service could not be stopped. I tried to stop it manually but that did not work. I called support but they just sent an email telling me to stop the service. What part of "I can't stop the service" did they not understand?
1 vote -
Include a description of the active filter settings used for the comparison in the report output
When generating a comparison to validate/review a deployment, you may use a fairly complex filter to identify the objects to deploy.
If you generate a report to send/configure to a third party, the filter settings you used to generate the comparison are not shown/output (looking at the Active HTML output specifically, but may be true across other formats).
The criteria used for the comparison are integral to the information being generated and should therefore be represented.
1 vote -
Single object deployment
When you right click on an object to see the deployment script and other options, include options for running immediately the script to target database. (to make it more interesting,to run the change script to any of the 2 compared databases).
Also, this should be dome on the right and left scripts at the bottom of the page.
Thanks6 votes -
Make the script for execution writable
Make the script for execution writable. It would be faster to be edited in you editor that is already connected to the target database and saves time . The alternatives (save or copy) are more time consuming
4 votes -
Change scripts should have existence checks on every object they add - tables, constraints, etc.
I've encountered this, especially with default constraints. I generate a change script. I run it on a system. Something happens that causes the script to fail. I fix the problem, but then it fails the second time because the default constraints it is trying to create are already there!
4 votes -
Option to Ignore "WITH EXECUTE AS CALLER"
The only difference in our comparison of the numerous tables is the "WITH EXECUTE AS CALLER". Add option that will allow to ignore this options
1 vote -
Allow to view objects excluded by filter
Both SQL Source Control and SQL Compare tell me how many objects are excluded by the filter. I can click on the link (button in SQL Compare) to see my filter settings. What I do not seem to be able to do is view the diff for excluded objects. Can you please add a button (or similar) to the UI of SQL Source Control and SQL Compare, that will allow me to toggle the diff table content between included and excluded objects.
4 votes -
Add "use <<Database>>" as an option in SQL Data Compare
This option exists in SQL Compare but not SQL Data Compare.
4 votes -
Avoid creation of Recovery tables
Please give an option to ignore Recore tables creation. I am trying to use SQLCompare in DevOps model to avoid long release timings. But if there is any data type change to a huge table then current concept of creation of recovery tables is disabling all the FK's, removing indexes and eventually creating a new table. This is very long process and not benefitting the projects. There should be an option to avoid the creation of Recovery tables. Please think in that perspective.
16 votes -
Ignore DEFAULT(X) column constraints
Replicated (push) tables do not contain default column constraints on the subscriber which are identified as breaks within SQL Compare 10. Provide the ability to ignore DEFAULT(X) properties on column within the UI.
108 votes -
compression
When applying data compression differences (table or index), use rebuild partition or rebuild index rather than drop & create, both to minimize impact, and in the case of primary keys on replicated tables, avoid failure because replicated tables can't be dropped.
e.g.,
ALTER TABLE schema.TableName REBUILD PARTITION = ALL WITH (DATACOMPRESSION = PAGE);
ALTER INDEX [IndexName] ON schema.TableName REBUILD PARTITION = ALL WITH (DATACOMPRESSION=PAGE);1 vote -
When deciding to synchronize some objects, at the first screen of the wizard must exist a check-box for not checking for dependencies
When deciding to synchronize some objects, at the first screen of the wizard must exist a check-box for not checking for dependencies, if checked (also I would like this to be the default behavior). This should allow the wizard not even to check for dependencies, which could be faster
1 vote -
risk
There are some changes that are riskier than others, not because of the type of change, but because of the object. For example, some changes require rebuilding a table or index. This can be a simple process if there are a few hundred rows, but it's a risky, slow process if there are a few billion.
It would be nice to add a "risk" value to certain tables, so that when I see a list of changes, I can determine if this particular object ought to be separated out as a different deployment.
6 votes -
Problem printing the interactive report
When I print an interactive html report to a color printer, some texts and images of the header come out printed, and the green, red and yellow colors of the types of differences are lost.
1 vote -
find wildcard
plz, add filtering object names by wildcards(* ?) in find box.
thanks...1 vote -
Attempts to add columns to table after dropping it in generated script
I just updated to SQL Compare version 13.4.0.6563 and tried to generate an update script for a database.
Several tables should have had two columns added to them but there seems to be a bug as the generated script followed these steps for each:
1 Drop primary key
2 Drop table
3 Add columns to table3 votes -
Possible bug -- changed behavour of Swap left and right button on the data sources page
In the latest version (updated this morning), the swap button changes server names, etc. shown in the header part of the page (source and target), but leaves info filled in on the bottom half alone. Can be confusing as to which server/database/etc. will be the source/left side and which will be the target/right side.
1 vote -
Compare View with a table
just like in sql data compare, it would be nice to compare a view with a table.
1 vote -
Add Ignore whitespace in string literals option
The behavior of the "Ignore whitespace" option was changed in version 13.3:
SC-9967: "Ignore whitespace" option is no longer applied to string literalsThis option would retain legacy functionality by adding the ability to still ignore whitespace in string literals.
3 votes
- Don't see your idea?