245 results found
-
Make the Print Command on Deployment Scripts Optional
Hello,
We use your compare utility to deploy update's to our software. We have many many changes to our Tables/Views/Procs/etc.In each of our deployment scripts there is un-needed Print '......' & Go commands that we don't need.
It would be nice to have the option of not having these print commands
21 votes -
137 votes
-
Project Options - option to ignore parameter default values
Project Options - option to ignore parameter default values. i.e. @fundid INT = 150 and @fundid INT = 152 on 2nd db is diff, option to ignore as may want to have different defaults per db but otherwise check sp.
8 votes -
Compare instance level information
Like configuration settings, security info (logins, server roles...), linked servers, jobs, SSIS catalog info for SQL2012 (folders, environments, security, projects, packages...) etc.
42 votes -
Compare tab contents!
I have yet to find a tool to compare the contents of two tabs in SSMS.
Ideal would be the ability to run an executable on the temfiles of two tabs. So the user could use diffmerge or whatever they liked, But any diff-function would be greatly appreciated.I don't know if SQL Compare is the right place, but it could be.
4 votes -
Add a Rollback Script Save option for both SQL Compare & Data Compare
In order to create a rollback script, we currently need to reverse the direction of deployment, save the rollback script, cancel the deployment, change the direction, then proceed with deployment in the correct direction. It would be great if the same screen on the Deployment Wizard would allow you to save BOTH a change script and a rollback script.
105 votes -
Reuse Open SSMS for deployment scripts
When selecting the option to open the deployment script in SSMS Compare opens a new instance of SSMS for each script that you generate.
In place of that would it be possible to open the scripts in an existing SSMS instance that is open already? This would make things a lot easier when generating multiple scripts.
35 votes -
Ability to selectively ignore column defaults
I'd like to be able to compare two databases, yet ignore certain column defaults in my comparison
20 votes -
Choose source control label as a version of a data source
Today, SQL Compare allows for two options when selecting a version of a source control data source - latest (head), or any other change set. It would be great if there was a third option: to select a version by label. We use labels as a means for controling which code is promoted from development to test to production. Anything ready to promote is labeled as “build ready.” It would be great to use this build ready label when selecting the version from the repository.
57 votes -
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 -
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
- Don't see your idea?