70 results found

1. Support "Ignore Column Order" in comparison window

   If the only difference between two tables is column order, the the table shows under Identical Objects section. But if column order AND something else is different, the comparison window hilights the out-of-order column.

   170 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   14 comments  ·  Delete…  ·  Admin →
   completed  ·  Tugberk responded

   We have completed this as part of https://documentation.red-gate.com/display/SC12/SQL+Compare+12.4+release+notes

2. Run SQL Compare on Linux/Mac

   I know weird to with a MS SQL Server, but many people who have been on the platform for a while now have developers with Macs, and automation systems on linux. DLM Automation is pricing some of us out of the Redgate ecosystem. With SQL server now running on Linux seems a reasonable path. I sure hope our beloved sql compare is not going away :(

   160 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   13 comments  ·  Delete…  ·  Admin →
   completed  ·  AdminTim Dalton (Product Manager, Redgate) responded

   On 4th September we shipped SQL Compare 14, including a Linux command line beta.

   You can find more information in our release notes, and please do get in touch with any feedback or requests for improvements!

   https://documentation.red-gate.com/sc14/release-notes-and-other-versions/sql-compare-14-0-release-notes

   Tim

3. Format compare using SQL Prompt format

   Ability to format the source and destination code to ensure compare is using the same structure.

   157 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   12 comments  ·  Delete…  ·  Admin →
   completed  ·  AdminStephanie (Product Manager, Redgate) responded

   In SQL Compare v14.7, we've added a SQL Prompt view tab on the differences pane.  We hope this helps you understand actual differences and not just differences due to formatting.  

   
   

   You can learn more at https://documentation.red-gate.com/sc/reviewing-the-comparison-results/viewing-the-sql-differences.

4. Separate primary key from other indexes for ignore index option.

   Our indexes are tuned and maintained in production. Database development is done elsewhere and moved using SQL Compare. Therefore we don't want to compare indexes. However, if we don't compare indexes, then the primary keys are not created. If we do compare indexes, there is a real risk that production will be damaged.
   This problem could be prevented by treating primary key indexes differently from other indexes. That this is even necessary is an implementation quirk of SQL Server.

   126 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   6 comments  ·  Delete…  ·  Admin →
   completed  ·  Andrew Farries responded

   In SQL Compare 12.2.3.4239, released today, we have made a start on giving users more fine grained control over exactly which indexes are deployed.

   We have added a new `Ignore performance indexes’ option which will ignore all indexes except primary keys and unique constraints.

   We realise that there is more we can do in this area, so we would like to hear your feedback about whether this new option is helpful and how we can do more.

   Feedback on this feature can be posted on the forum thread:

   https://forum.red-gate.com/discussion/80770/new-feature-ignore-performance-indexes

5. Add support for External Tables

   I use Azure SQL, and there is limited cross-database functionality in that environment. Due to this I have several External Tables that I use to point to a Master Database with shared setting, info, etc. for each customer database.

   When I used SQL Compare to fill out the schema for a new database it copied all of the External Tables as Local Tables, and it didn't bring over the Data Source either. This could be very handy as dealing with external tables (and especially changes to them) is a pain.

   119 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   6 comments  ·  Delete…  ·  Admin →
   completed  ·  AdminTim Dalton (Product Manager, Redgate) responded

   We shipped support for External Tables in SQL Compare 14.5.
   Please turn on frequent updates to get this version
   https://documentation.red-gate.com/sc/upgrading/turning-on-frequent-updates
   For more information, see the release notes:

   https://documentation.red-gate.com/sc/release-notes-and-other-versions/sql-compare-14-5-release-notes

6. Ignore change tracking

   Simple really, allow an option to ignore the change tracking options on tables

   111 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   6 comments  ·  Delete…  ·  Admin →
   completed  ·  Michelle Taylor responded

   We’ve added an Ignore Change Tracking option in Frequent Update 13.4.2.6669 (now available on the main update channel in 13.4.8.7337).

   You should be able to get this version now with Check for Updates if you have a valid support and upgrades contract.

7. Display Last Modified

   I've asked for this many times since SQL Compare 7.

   Please allow us to see the Last Modified Date on the objects. The information is VERY easily obtained.
   
   select objectid, Modifydate from sys.objects where type='P'

   It would be very useful and beneficial to see.

   105 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   11 comments  ·  Delete…  ·  Admin →
   completed  ·  Andrew Farries responded

   We have just released an update to SQL Compare V12 on the Frequent Updates channel containing this feature. For tables, views, functions and stored procedures the comparison grid will show an extra column indicating when the object’s schema last changed.

   Feedback on this is best posted on the forums:

   https://forums.red-gate.com/viewtopic.php?f=200&t=80289

   We are interested in hearing whether this solves your problems and about any further improvements we can make.

8. multi factor

   Support Azure AD auth using MFA

   93 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   7 comments  ·  Delete…  ·  Admin →
   completed  ·  AdminTim Dalton (Product Manager, Redgate) responded

   We shipped Azure Active Directory Interactive Authentication as part of Compare 14.2.

   https://documentation.red-gate.com/sc/release-notes-and-other-versions/sql-compare-14-2-release-notes

9. SQL Compare store options for index create\rebuild

   First this may be more apparent as tedious in my case, we happen to have large tables with decent sized indexes. I would appreciate if through the setup of a SQL Compare project I could impact index create or rebuild behavior through the selection of on\off toggle for the switches that are available upon creation of an index.

   I use some options more than others with the most frequently added option being SORTINTEMPDB = ON. I use this because when building large indexes I want to try and avoid as much as possible any unintended file growth by specifying that TempDB is used for the sort operation of the index create.

   Since there isn't a mechanism to specify this in the project options, I must always generate a deployment script and manually modify the index create portions of a given script to specify any switches I want to throw at the index create.

   So for each possible modifier:

   PADINDEX = ON
   STATISTICSNORECOMPUTE = ON
   SORTINTEMPDB = ON
   DROPEXISTING = ON
   ONLINE = ON
   ALLOWROWLOCKS = ON
   ALLOWPAGE_LOCKS = ON

   I would like to be able to select that these options be used and specify the value (ON or OFF). Since this is a project level setting, I could then set the desired values as a project default ensuring that when the deployment is done through SQL Compare or a generated migration script that I don't have to step through each index create and add the options I want to use manually.

   Using the previously listed modifiers as an example in that all are turned on, the deployment script for an index would include the following:

   CREATE NONCLUSTERED INDEX [IDXIndexOne] ON [Schema].[Table]
   (
   [Column1] ASC
   )
   WITH (
   PADINDEX = ON, STATISTICSNORECOMPUTE = ON, SORTINTEMPDB = ON, DROPEXISTING = ON, ONLINE = ON, ALLOWROWLOCKS = ON, ALLOWPAGELOCKS = ON
   )

   GO

   First this may be more apparent as tedious in my case, we happen to have large tables with decent sized indexes. I would appreciate if through the setup of a SQL Compare project I could impact index create or rebuild behavior through the selection of on\off toggle for the switches that are available upon creation of an index.

   I use some options more than others with the most frequently added option being SORTINTEMPDB = ON. I use this because when building large indexes I want to try and avoid as much as possible any unintended file growth by… more

   78 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   10 comments  ·  Delete…  ·  Admin →
   completed  ·  AdminTim Dalton (Product Manager, Redgate) responded

   We shipped this as part of SQL Compare 14.1.3

   https://documentation.red-gate.com/sdc/release-notes-and-other-versions/sql-data-compare-14-1-release-notes

10. Support SQL Server 2014
    46 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    completed  ·  Jonathan Watts responded

    We have now released SQL Compare v11 which contains support for SQL Server 2014 including support for Memory Optimized OLTP objects,

    You can download the latest version from http://www.red-gate.com/products/sql-development/sql-compare/

11. Connecting to SQL Database By Using Azure Active Directory

    With Azure SQL Database there is an option to connect by Azure AD account. It is one of the first citizen authentication type in Microsoft Management Studio 2016.

    I suggest adding this types of authentication into RedGate products (especially into Compare and Data Compare).

    Details here: https://azure.microsoft.com/cs-cz/documentation/articles/sql-database-aad-authentication/

    45 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    completed  ·  Tugberk responded

    Hi!

    As part of v12.4.9 release (frequent updates release), SQL Data Compare and SQL Compare now support Azure Active Directory authentication with integrated and password authentication methods. These options are available in the ‘Authentication’ dropdown in the ‘Database’ section of the ‘Edit project’ window. Note that this feature requires .NET 4.6 and adalsql.dll to be installed; see https://docs.microsoft.com/en-us/azure/sql-database/sql-database-aad-authentication-configure#configure-your-client-computers for more details

    Let us know what you think!

12. distinguish between unique and non-unique indexes

    (This is actually relevant to both SQL Compare and SQL Source Control.)

    We really need to be able to distinguish between unique and non-unique indexes when comparing, checking in, and deploying database schema changes. ("Unique indexes" include primary keys, unique constraints, and unique indexes on tables and unique indexes on views; "non-unique indexes" include non-unique indexes on tables and views.)

    Unique indexes are essential to the database development process. They make a significant functional difference to the behavior of the database: they enforce business rules and referential integrity; they limit the data that can be entered into the database; foreign keys depend on them. Developers should be responsible for creating and maintaining all of the unique indexes on the development database, and an automated deployment process that uses SQL Compare and SQL Source Control should be able to deploy all database schema changes, including unique indexes, from the development database to the production database.

    On the other hand, non-unique indexes do not affect the database's behavior; they only affect the database's performance. Developers should not be responsible for maintaining non-unique indexes; they can't. A development database usually has a relatively small amount of test data in it, and a production database usually has a much larger amount of real data. SQL Server uses different indexes and different query execution plans depending on the amount and quality of data in the database, and the servers recommend different indexes depending on which queries get used the most frequently. A developer, running queries on the development database and looking at the execution plans to determine which indexes are needed, will get results that are not valid for the production database. In our case, it is also common for one set of queries to be heavily used one month and an entirely different set of queries to be heavily used the next month, so the developers would never be able to keep up with the production server's changing needs.

    Instead, we have a SQL Agent job that runs periodically on the production server to maintain non-unique indexes. The job reads and analyzes the system view sys.dmdbindexusagestats to determine which indexes are the least-recently used and the most-frequently updated, and drops them. It also reads and analyzes the system views sys.dmdbmissingindexgroupstats, sys.dmdbmissingindexgroups, and sys.dmdbmissingindex_details to determine which missing indexes are the most needed, and creates them. This index maintenance job frees up developers to do actual development instead of tracking down performance problems and fixing them.

    The problem is that SQL Compare and SQL Source Control do not distinguish between unique indexes and non-unique indexes; it will compare and synchronize either all of them or none of them. If we ignore indexes, then we can't deploy primary keys, unique constraints, unique indexes, or foreign keys (since foreign keys depend on unique indexes); if we include indexes, then the non-unique indexes created on the production server will be dropped in favor of the non-unique indexes that happen to exist on the development server, undoing all of the performance improvements made by the automatic index maintenance job.

    We would like the "Ignore indexes" option of SQL Compare and SQL Source Control to be split into two options, "Ignore unique indexes" and "Ignore non-unique indexes".

    (This is actually relevant to both SQL Compare and SQL Source Control.)

    We really need to be able to distinguish between unique and non-unique indexes when comparing, checking in, and deploying database schema changes. ("Unique indexes" include primary keys, unique constraints, and unique indexes on tables and unique indexes on views; "non-unique indexes" include non-unique indexes on tables and views.)

    Unique indexes are essential to the database development process. They make a significant functional difference to the behavior of the database: they enforce business rules and referential integrity; they limit the data that can be entered into the database; foreign… more

    27 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Delete…  ·  Admin →

13. Allow SQL Compare to ignore name differences in Default Constraints

    Since default constraint names are system generated, they may have the same defintion but a different name.

    22 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    3 comments  ·  Delete…  ·  Admin →
    completed  ·  Michelle Taylor responded

    The ‘Ignore System named constraint and index names’ option should address this issue, unless I’ve misunderstood?

14. 64-Bit Version

    Create a 64-bit version of SQL Compare.

    21 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    3 comments  ·  Delete…  ·  Admin →
    completed  ·  AdminMichael Upton (Development Lead, Redgate) responded

    Version 11.2.2.23 of SQL Compare and SQL Data Compare (currently available via frequent updates) will now run as 64 bit processes in a 64 bit environment.

    See http://documentation.red-gate.com/display/SC11/Turning+on+Frequent+Updates for details on how to enable Frequent Updates, and http://documentation.red-gate.com/display/SC11/SQL+Compare+11.2+release+notes for the latest release notes.

15. Include 'IF EXISTS' in the generated scripts

    The ability to include an option for 'IF EXISTS' based on the object type. The IF EXISTS would need to be generated per database object. This would greatly assist in cases where you have 'similar' yet slightly different environments that you expect to be the same, yet may have had a patch applied early etc.

    You would need to be able to specify whether you drop and recreate, leave alone, or anything else that might make sense.

    Thanks,

    Nick

    19 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    completed  ·  AdminMichael Upton (Development Lead, Redgate) responded

    The ‘Add object existence checks’ option (Options—>Behaviour—>Add object existence checks) should do exactly this.

    If there are specific cases where that option is not working, please email support@red-gate.com to let us know.

16. Ignore MASKING FUNCTION on columns

    Dynamic masking functionality is new to SQL 2016. It is applied on columns.

    https://docs.microsoft.com/en-us/sql/relational-databases/security/dynamic-data-masking

    Great for DEV and UAT environments where data obscurity is required.

    CREATE TABLE Membership

    (MemberID int IDENTITY PRIMARY KEY,

    FirstName varchar(100) MASKED WITH (FUNCTION = 'partial(1,"XXXXXXX",0)') NULL, *ignore these

    LastName varchar(100) NOT NULL,

    Phone# varchar(12) MASKED WITH (FUNCTION = 'default()') NULL,

    Email varchar(100) MASKED WITH (FUNCTION = 'email()') NULL);

    Ideally we need this ignored in SQL Compare and SQL Source control comparisons so it is not accidentally deployed to production.

    18 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    completed  ·  AdminTim Dalton (Product Manager, Redgate) responded

    Thanks for the suggestion David, this was released today in Compare 14.1.2.

    Any feedback or further suggestions do let us know.

    Tim

17. Please fix columnstore index comparisons

    Currently SQL Compare detects the order of columnstores as a difference. Columnstores have been around for a while now, can't this please get fixed?

    18 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    completed  ·  AdminMichael Upton (Development Lead, Redgate) responded

    I’m glad to tell you that this was fixed in Compare v11.0. If you’re using a later version and are still having trouble, please contact support@red-gate.com for help.

18. Bring back the Project Browser in Compare 12

    The Project Browser, that could be opened at startup, was replaced in Compare 12 with a much less useful standard Open File Dialog. Please bring back the browser. See also, https://forums.red-gate.com/viewtopic.php?f=200&t=80066

    18 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    4 comments  ·  Delete…  ·  Admin →
    completed  ·  Mark Jordan responded

    We’ve now brought back the project browser as an option in the latest release: see https://forums.red-gate.com/viewtopic.php?f=200&t=80430 for more details

19. Use "My Defaults" by default even when coming in from SSMS Integration

    I have have set "My Default" options then these should always be used, regardless of how I come to the project (but especially for any new projects). Currently if I launch SQL Compare from SSMS integration the Red Gate Default options are used.

    Steps to reproduce:
    Select a database, right click > Schema Compare / Deploy
    Drag a database over for the Target
    Compare/Deploy with SQL Compare

    Expected:
    SQL Compare uses "My Default" options
    (I have Ignore > Permissions)

    Actual:
    SQL Compare uses Red Gate Default options

    17 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    completed  ·  AdminDavid Eadie (Software Engineer, Redgate) responded

    I’m pleased to say this has been implemented as part of SQL Compare 12.

20. sqlsompare report

    xml, html and excel reports for database differences (using options) include everything similarities as well as differences. Since, xml is excellent way to import data to SQL, it would be great if those reports included only differences (so that the file size is smaller). Right now the differences can only be output to text file if I am not mistaken.

    13 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    completed  ·  Michelle Taylor responded

    When you generate a report, there is a check box just above the last line in the dialog ‘Also include identical objects’ – if you uncheck this, then only differences will be output in your report.