250 results found
-
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 -
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 -
Add an 'Ignore owner/schema' option to SQL Compare
I'd really like this ignore option, so that [UserA].[Table] on the left hand side would match with [dbo].[Table] on the right hand side. There obviously needs to be a warning that this won't work unless table names are unique between owners/schemas (which, in my experience, they usually are).
26 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 -
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 -
Add a "source option" for nuget package store
It can be very useful to add an option for reading from a nuget package store, in addition to "Direct From Source Control" and "Scripts folder".
The package should be reached unsing the http url. This is useful when reading from a build server outcome, which can upload the packages to the nuget store.33 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 -
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 -
Option to ignore SQLCMD variables in SSDT scripts
Any differences involving usages of SQLCMD variables would be ignored with the option turned on.
16 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 -
Show/deploy static data changes in SQL Compare UI
Please add an option in the UI of SQL Compare to include static data. This would be equivalent to the command-line option "Include:StaticData"
If selected it would compare and deploy data changes to the target DB (along with the schema changes), and ideally it could also link the static data table in the target DB if not already linked. Use case is where a new table is created and linked in a dev branch and you want to deploy to trunk.
27 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 -
Ignore database variables used in Visual Studio Project
There are cases when for continuous intergration we use Visual Studio Project 2013 to build our databses. Sometimes we need to use database variables these look like: [$(DatabaseName)]. Though Visual Studio can recognize it as a variable, redgate will not and will output that as it is for deployment or comparison.There need to be an option where these variables can be ignored or output using the variable name which is specified in the project.
10 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 -
option to ignore case in schema name compare
In version 11.1.30.30, I have 2 database where objects only differ because on schema has names that are camel cased and the other is all lowercased; everything else is identical but keeps showing in list of 'objects tat exist in both but are different'
7 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 -
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 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
- Don't see your idea?