250 results found
-
Separate ifg in the SQL Compare Options
Please break out the ifg switch in SQL Compare Options so file groups are separate from partition schemes and partition functions. Maybe ifg only ignores file groups, and create a second name ifp (or whatever) that would ignore only partition schemes and funtions.
1 vote -
Database scoped credentials are missing
SQL Compare ignore database scoped credentials. So you wont be able to create external data source from generated script. It's clear that password is not accessible. But if you prepare create statement with data available from sys.databasescopedcredentials and let us fill out secret it will be much better then to skip this object.
1 vote -
Left justify both Object Name columns
We prefix our objects with certain characters, so to right-justify the left Source "Object Name" column names makes it hard to visually read down the list of objects to find something in particular.
3 votes -
Rebuild partition instead of dropping & recreating primary key when only changing data compression
SQL Compare currently attempts to drop and recreate a primary when changing compression.
REBUILD PARTITION ALL WITH (DATA COMPRESSION PAGE|ROW|NONE
would be more efficient and less intrusive since, among other things, it doesn't require dropping and recreating all foreign keys.2 votes -
Synapse Compatibility
Can the compare engine be enhanced to work with Azure Synapse?
15 votes -
Compare the OPTIMIZE_FOR_SEQUENTIAL_KEY property of an Index
By default this is 'off' in SQL 2019. But we have found some tables have significant performance improvements for load if its 'on'. Thus tuning requires these indexes to be on. For SQL Compare to remain useful it needs to highlight were where there is a difference in the property - and support deployments with the property to retain it as on.
1 vote -
Ability to define two SQL logins as being the same
We have separate SQL Server service accounts for each environment. For example, saSQL01prod and saSQL01test and saSQL01dev. We want to ensure that the same permissions in PROD exist in TEST. However, now, SQL Compare wants us to create the saSQL01prod account and remove the saSQL01test account to equalize.
What we wish to happen is that it compare the permissions of the saSQL01prod account in our PROD environment to the saSQL01test account in our TEST environment and generate the compare based off that.
For example, saSQL01…
10 votes -
Include option to only include diffs
The idea here is produce a summary - that is the content focuses on the changes.
For example:
For new objects - indicate "new", with one-line description - but do not include definition
For deleted objects - indicate "removed"
For changed objects - only the show the "diff" with a little context instead of the complete definition.1 vote -
Script Generation: Control over the sp_rename of a table
When you add a non nullable column in a table, there is a warning that the script can fail. The generated script will issue will try to help by removing all contraints, rename the table and recreate it. This cannot be done on large table (with data). The only choice I have is to add the column as nullable, add the initialisation in the script and make it not null after. So, I would like to accept the warning and to let the 'alter table add column' been generated with a comment in the generated script. I guess to work…
1 vote -
Object permissions in separate files instead of inside object definition
Presently, when syncing database to folder, all object permissions are stored inside object definition files. We would like to change the way permissions are stored; we would like to have an option to store object permissions in separate files.
For example, the following entry appears in dbo.A.sql file:
CREATE TABLE [dbo].[A]
(
[b] [int] NULL
) ON PRIMARY
GO
GRANT SELECT ON [dbo].[A] TO [role_x]We save data into folders which are then checked into GIT as branches. Or goal is to be able to track all table changes in branches before merging into master branch, which is automatically deployed…
8 votes -
User Permissions
I would like the option to compare user permissions, or system tables/views.
1 vote -
SQL Compare should support Always Encrypted
I made a copy of a database for my application and implemented SQL Always Encrypted in the copy database. I did a compare back to the original, intending to get a deployment script to get those changes back into the original DB and SQL Compare isn't seeing the details of the columns related to encryption. I saw a message board post that indicated this isn't supported, but would like to request that support for this be added
6 votes -
Menu bar display issues when using Remote Desktop app in Windows 10
I have trouble seeing the menu bar when using Remote Desktop app in Windows 10. The menu bar is very tiny and not completely visible. Very hard to work with.
1 vote -
SQL Compare Timeout for batch jobs
We really need the ability to specify big timeout periods as we're dealing with large tables with breaking changes (adding constraints) which require rebuilding the table, and we have no luck completing the task due to short timeout in SQL Compare.
4 votes -
Excluding a role in v. 14 should exclude its permissions as was the case for v. 13
Using the SQL Compare v. 13 CLI to exclude a role that exists only in the target database used to also skip permissions granted to that role. The resulting script did not revoke the role's permissions in the target. Now, in v. 14 (14.4.11.17350), excluding the role only keeps the role from being dropped. The resulting script revokes all permissions granted to that role in the target. We think this new behavior represents a defect that should be fixed. See my support request 225533. I am told there is a bug report that addresses this issue: SC-10183. However, I don't…
8 votes -
Open only once MS SQL Server Management Studio
Instead of opening SSMS every time I create a new script with the DEPLOY button, it would be nice to check if SSMS is already openned and then switch to it instead of opening a new SSMS each time, at the end of the day I have 20 SSMS open.
6 votes -
Enhance support for default constraints
I need to replicate a database for read-only reporting purposes and the production database is littered with all sorts of default constraints.
For example:
ALTER TABLE [schema].[table] ADD CONSTRAINT [DFtablecolumn] DEFAULT ('Unknown') FOR [column].
This is what the definition is in SSMS.In SQL Compare:
[column] [varchar] (15) COLLATE SQLLatin1GeneralCP1CIAS NOT NULL CONSTRAINT [DFtable_column] DEFAULT -- No text is available,
Now the constraint fails AND the comma separator for the next line is missing.
Another fun one:
[SCD Surrogate Hash Key] AS (CONVERT([varbinary](64),hashbytes('SHA2_512',coalesce(CONVERT([varbinary](50),[column]),0x00)+0x0001))) PERSISTED NOT NULL,
And SQL Compare loses all track…
4 votes -
1 vote
-
No error should be reported when two databases are identical
While using command line to generate a difference report (in html format), if the two databases are identical, the console output says:
Error: The selected objects are identical or no objects have been selected in the comparison. Use /include:Identical to suppress this error.
If I include the /include:Identical switch, then the error is not reported on the console, but the output html file has all the objects in it.
I don't want the console error as well as don't want the identical objects in the html file. This is what I want:
- Don't want to use the /include:Identical switch
- If…
12 votes -
Support for Module Signing Comparison
Please could you consider adding support for the comparison of signatures between databases. Currently SQL Compare doesn't check for differences between module signatures, please refer to this forum post:
https://forum.red-gate.com/discussion/87404/module-signing-support
The consequence of this is that during deployment by SQL Compare, module signatures will be ignored, therefore causing deployed modules that depend on the signatures to fail during execution.
Additionally, should signatures be removed from a database using a command such as sp_refreshsqlmodule (which implicitly removes signatures), SQL Compare will not identify that the signatures have been removed.
1 vote
- Don't see your idea?