252 results found
-
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 the scrolling view…
1 vote -
Allow filters to be case INsensitive
Allow filters to be case INsensitive
When I add a filter e.g. schema name begins with "ABC" then objects with schema Abcdef will not be shown even though i have opted for case insensitive matching
this means that I have to make several OR filters to cover all combinations of upper or lower case letters1 vote -
excel
Include attributes to be changed in an object to an excel report in sql compare. include not only the object name to be changed but the actual change to fields
within the object or the script change to be made for programability items users roles and permission. e.g. Database.schema.objectinsource.change(details of change column to be altered in a table its original value its new value its datatype and length its nullability and any default constraints.1 vote -
beyond
Allow an object / script comparison to be opened in an external Diff viewer, such as Beyond Compare. Provide configuration settings to configure external diff viewer EXE, similar to what source comparison tools do.
1 vote -
Add next to table object names the record count in the table
When comparing tables I saw that for two tables auto-map has mapped some columns. Since I know the tables are not compatible I had to check that the target does not have any rows in the table. Please add some indicator on the object list so that I can know easily if there are any rows in the table
1 vote -
user defined type
I recently had to use SQL Compare to create a rather large add new and update deployment script.
I was pleased that it picked up User Defined Types in addition to the normal tables and stored procedures.
But it did not pick up the permissions for the User Defined Types, and that was a failure point when executing the stored procedures.
This was my first time working with User Defined Types before, and I thought it odd they needed permissions at all. I did not apply any in the development environment, and they worked there.
But the error was clearly…1 vote -
Allow migration of Indexes ONLY
I have multiple databases which have the same columns (mostly) but sometimes differing defaults.
They also have different indexes.
I'd like to choose to ONLY sync indexes across.
Obviously the system would need to be intelligent enough to sync only those that have the columns they use/include in both source and destination.
1 vote -
SQL Data Compare\SQL Compare between SQL database tables and Azure Synapse Serverless database external tables
It would be great if SQL Data Compare/SQL Compare work with External Tables in Azure Synapse Serverless database.
1 vote -
Add support for SQL Server Management Studio 20.
If I open up Tools --> Application Options in SQL Compare, I see SQL Server Management Studio 19, but not 20 which has been out for months now. And I believe it is the same in SQL Data Compare as well.
1 vote -
Suppress Ignored Statement Warning
When using SQL Change Automation command line, it would be helpful to suppress warnings for ignored statements. Since these scripts are checked into source control, these warnings will get long over time with addition of more scripts.
1 vote -
Use the SQL Prompt setting when generating a new compare
When I generate the HTML report that it defaults back to the old view. Then simple formatting differences is shown, which were not part of the interactive view when using the SQL Prompt setting.
1 vote -
debug logging
I've recently hit a problem when using SQL Compare (which was logged as request #322451).
I am reasonably sure the issue is with the database, not the tool, but when using debug logging, there's just not enough information to understand why it gets stuck on "reading object text (99%)" for over 20 minutes for a specific database, yet is very fast on other similarly sized databases.
Some additional logging during the comparison phase might help to work out why this is happening.
1 vote
- Don't see your idea?