239 results found
-
/force command no longer creates directory if it does not exist
In previous versions of SQL Compare the /force switch would create the entire file path that was specified for the report output. In version 13, if any of the path does not exist the report generation fails for a 'Could not find a part of the path' error. Only if the path and the file already exist, will the /force switch work.
4 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 -
Add Summary View command line option
Currently there are 3 output options when running sql compare via the command line /quiet /verbose and the default. I'd like to see an option between the default and verbose logging similar to the "Summary view" present in the main application.
For example: I'd like to see the tablename that has diffs (default option) AND the name of the index on said table that is different (new summary option), but not the entire table definition (verbose option).1 vote -
Ignore indexes option should not query indexes
If indexes & partition schemas/functions are set to be ignored, SQL Compare should not attempt to query them. Additionally would be helpful for other object types that are ignored so that the queries are streamlined to only what is selected for compare. This would be a performance enhancement, the pain is where there is a high number of partitions where the intention is just to compare something simple like stored procedures and UDFs.
1 vote -
Flter save location does not exist causes exception
After you specify a file path and save your filter.
Delete the directory where the filter was saved
Click the "Save" button again and you get an exception. Need a "Save As" function or something to override the setting you set last time.1 vote -
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.
28 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
- Don't see your idea?