260 results found
-
Ignore Database Name in Stored Procedures, Views, and Functions
We have 3 environments for one of our core applications. Each environment has a different database name: dbproto, dbuat, and db_live for an example.
We keep all the SP, Views, and Functions we develop in a separate database so at no time do we alter the database supplied by the vendor. This database name is the same in all three environments.
Because of the name difference for the vendor database all the SP, Views, and Functions are flagged as different. The only difference for 95%+ of them have is the database name (eg dbproto vs dbuat).
…
14 votes -
Allow resizing the window from a remote desktop
When remote using Windows Remote Desktop, the main application window is not resizable. The resize cursor does not show when hovering over the edges or corners, and I cannot click and drag to change the size.
17 votes -
Test for database users before creating them
For example, add an "IF" as below:
IF NOT EXISTS (SELECT * FROM sys.database_principals where name = 'xxx\yyyyyy')
CREATE USER [xxx\yyyyyy] FOR LOGIN [xxx\yyyyyy]
GO7 votes -
The application window for SQL compare is very hard to resize...
Provide more support for resizing the app window...not the instance window ...that fine. The app window expands to the whole screen....this gives me the irrates as I need to get at stuff behind the SQL compare window
7 votes -
ignore timestamp - binary 8 differences in databases
It is an option in sql replication to map rowversion/timestamp columns to binary(8) columns. It would be a nice option for sql compare to allow for this difference between databases. Without it every table is flagged up as being different which is a headache.
9 votes -
Excluding a user should also exclude their mappings to roles
Using SQL Compare version 11 for Microsoft SQL Server, I can exclude a user from the schema comparison:
<exclude>Role:MyCustomUser</exclude>
This works fine for excluding the user.
However, the comparison engine does not exclude the user's mapping to roles. The script includes sp_addrolemember commands for the excluded user.
When excluding a user, I expect their role assignments to also be excluded.
I suspect this behavior may exist with object exclusions for other object dependencies. Have not tested other scenarios.
13 votes -
Option to ignore SQLCMD variables in SSDT scripts
Any differences involving usages of SQLCMD variables would be ignored with the option turned on.
18 votes -
ER Diagram Tool
It would be really cool if RedGate would consider building an ERD Tool that would allow you to visually design your database schema using drag and drop before deploying to SQL Server (either generating the deployment script or deploying directly from the application)
25 votes -
compare two different commits from GIT
Add support for comparing two source control commits through the UI.
Currently this requires cloning a second repository to perform the compare.
16 votes -
Add an option to ignore the Unicode differences in Extended Properties.
Add an option to ignore the Unicode differences in Extended Properties. SQL Compare currently will differentiate between Extended Property text (e.g., for MS_Description) created as Unicode vs Ansi (e.g., N'My text' vs 'My Text'). SQL will apparently maintain this different even though scripts generated from SSMS always show it as Unicode (with N). Thus, this can cause SQL Compare to show differences between two databases where there is none intended (the description text is identical).
5 votes -
Compare database settings such as snapshot isolation
Have SQL Compare be able to compare database level settings in sys.databases such as isolation level
12 votes -
Support for Replicated Databases
I would like to push schema changes to a transactionally replicated database. Now, SQL Compare breaks replication when I push schema changes. Please add support for sprepladdcolumn and sorepldropcolumn rather than ALTER TABLE.
117 votes -
Allow Comparison of CDC Objects
CDC (Change Data Capture) objects are currently excluded from comparison.
Because SQL Source Control uses SQL Compare behind the scenes, this means that CDC objects cannot be committed to source control, which in turn means that databases containing objects (e.g. views) which reference CDC objects cannot be deployed with SQL CI.
I don't believe that SQL Compare should compare CDC objects by default, but there should be an option to allow it.
28 votes -
Filter Extended Properties on other objects than databases
It would be great to be able to filter extended properties on other objects than databases. We only want to compare certain extended properties on tables, but the Extended Property Filter only works on database properties.
This is similar to this idea: https://redgate.uservoice.com/forums/141379-sql-compare/suggestions/5680027-ignore-extended-properties-created-by-the-view-des (which would be solved by filtering out "MS_DiagramPane1" on the view)
And suggestion #2 in this forum thread: https://forums.red-gate.com/viewtopic.php?f=177&t=77849&p=136399
28 votes -
Ability to add additional connection parameters
In SQL Server management studio you have the ability to add additional connection parameters however there is no ability to be able to specify these in SQL Compare. This is a problem in SQL 2012 when trying to connect to availability group listeners that have replicas in multiple subnets. In order to connect to the availability group listener you need to specify the “MultiSubnetFailover=True” connection property, otherwise it results in a 50/50 chance of connecting successfully.
19 votes -
Compare on object
Need an option/ability to re-compare just one object like table, procedure,view or function etc. If my database contains 1000+ objects, if I modify one of them, there should be right click re-compare menu to just re-compare that one object. Instead of comparing the whole database. Comparing whole database take a bit of time when work remotely. Even though I have filters, it takes quite a bit of time.
29 votes -
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 -
138 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 -
Make SQL Compare Three-part identifiers aware and filterable
Not always a deployed database has the same name of the source database due to customers' naming conventions. So it'd be great if SQL Compare will be three-part identifiers aware, so that if you compare the same table from different named databases as following:
SELECT *
FROM MyDatabaseA.MyTableSELECT *
FROM MyDatabaseB.MyTableSQL Compare will not show them as different if you want a three-part identifiers insensitive comparison.
18 votes
- Don't see your idea?