249 results found
-
SQL Compare Flagged store procedure difference but could not see where
SQL Compare Flagged a difference between Test and Production Store Procedure but I could not see where. I had to use notepad++ compare to see a Single Space. Please make this visible in the next release.
1 vote -
I have found that User Defined Data Types are not scripted after stored procedures that use that data type.
I have found that User Defined Data Types are not scripted after stored procedures that use that data type.
3 votes -
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 -
Option to ignore rowguid column generated by Merge Replication
When SQL Server sets up merge replication it creates a rowguid column to maintain integrity between the tables of the publisher and subscriber. Typically this setup doesn't exist in non-prod environments which ends up generating false positives differences.
31 votes -
Bring back the side by side html output!!
Many people have stated this but the side by side html output was more helpful and saved more time for us.
23 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 -
compare multple databases
I'm going through an exercise of determining object changes between versions of an app suite containing 55 databases.
It would be nice to be able to specify which databases to compare during a single run instead of processing it one database at a time.12 votes -
Provide the ability to specify object permissions within custom filter rules
Currently (v 13), there is an all-or-none project option to include or exclude object permissions across all database objects. It would be fabulous to push that option down into custom filter rules so inclusions/exclusions can happen more granularly, at an object-level. Use case: the majority of our tables use generic permissions but a small subset of tables use ActiveDrictory groups that differ by environment so we have to manage them as a special case. I'd love to be able to specify something like this as a filter rule: 'generate object permissions for all tables except tables that begin with <blah>'.
4 votes -
Side by side compare.
Please bring back the compare results in a side by side compare with modify date as in compare version 12
19 votes -
I liked it they it was in Version 12. we could see side by side comparison. and also you used to show the last modification date
I liked it they it was in Version 12. we could see side by side comparison. and also you used to show the last modification date
4 votes -
give more information in header
The report header shows only the database name. Seeing BobsDB -> BobsDB isn't useful. I would rather have something like: DevServerName.BobsDB --> ProdServerName.BobsDB
6 votes -
automap link directly to view/edit table mapping
When SQL Compare apply an automapping on column name of a table, there is a little yellow image with "Auto Map" displayed on the table. It would be nice if a menu or double click or else would be availaible to open directly the column mapping of this table. It would be faster to see the mapping applied and correct it if needed.
7 votes -
HTML Comparison Results
Bring back the side by side html output, please!!!
27 votes -
Add option to ignore target only objects
When comparing two databases it would be nice to have the ability to have objects that only exist in the target be ignored. It is somewhat dangerous to have an option that would cause objects to be dropped and it would be good to be able to not have that show.
4 votes -
Comparing TFS Changesets
When comparing a TFS Changeset in SQL Compare it will show all schema changes that are different between the Changeset and the destination, but within a TFS Changeset, there is metadata within the Changeset to indicate which specific database objects are being changed within the Changeset. It would be a huge timesaver to allow SQL Compare to be able to only select the database objects that are actually being impacted by the Changeset by default. The situation I have is this:
Developer 1 - Adds a table to database A and checks in the change to the development database, but…
6 votes -
Display last change dates in top database strip
Display last change dates of repository for databases under SQL Source Control.
And display also last schema change date from database.
4 votes -
My projects - compare all projects
Add an additional "Compare all" button to compare all projects in the actual "Look in" folder. Show a simple is equal/different indicator on each project for the results.
Consider using VS-style solution files or kind of meta-scp.
This is somewhat similar to https://redgate.uservoice.com/forums/141379-sql-compare/suggestions/13517250-auto-compare-after-oping-a-project-mass-compare
6 votes -
Unecessary table rebuild
The tool will try to rebuild the whole table even when the only thing needed is the addition of one column. If you need it, I can send an image of the comparison results. To work around it, I search for rebuilds within the generated script and substitute them by the needed command, specially if the table is a very large one.
1 vote -
When comparing sequences, should be able to ignore the START WITH value
When comparing sequences, ANY difference triggers the program to indicate a difference. In reality, when it comes to sequences, the START WITH value changes with use. If two environments are being compared and one is used for different testing, or even as a production environment, the START WITH value will likely be different. This doesn’t mean the sequences are different and, in fact, can lead to serious problems for objects that rely on the next value in the sequence being unique. There should be a way to ignore the START WITH value when comparing sequences.
28 votes -
Add option for older version of HTML Report in SQL Compare 13
The new version of the HTML report is not as useful as side-by-side comparsions. I don't like the new version, and the developers like it even less. Thanks!
60 votes
- Don't see your idea?