69 results found

1. 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 →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   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/

2. filter with underscore in name doesn't work correctly (possible bug)

   When applying a filter with "Starts with underscore" it removes all entries with underscore in the name, even when they underscore is not at the beginning of the name. Please fix. My upgrade scripts missed important stored procedures because of this apparent bug.

   1 vote

   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 →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  AdminMichael Upton (Development Lead, Redgate) responded

   This problem has been fixed in version 11.2 (currently only available via frequent updates). We have added new ‘Like’ and ‘Not like’ filter match operators which honour all SQL LIKE wildcards, and changed the previous ‘Begins with’, ‘Ends with’, and ‘Contains’ to stop treating them as wildcards.

   You may need to edit existing filters to take advantage of the new behaviour.

3. 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 →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   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

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 →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   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. Deployment Wizard --> 3 - Review Dependencies Encorced Inconsistently

   This step is often skipped when I click on Next from Step 1. The Deployment Wizard will skip straight to '4 - Review Deployment Script'. This behavior is inconsistent: sometimes '3 - Review Dependencies' IS enforced even though it is skipped and other times it is not. In our situation, the rule is to NOT enforce dependency changes.

   This has bitten me several times in the past, so I now always click on Back when on Step 4 to see if Step 3 was enforced or not. Of three deployments today requiring SQL Commpare, two of them exhibited this behavior. Had I not known about this, I would have introduced unwanted AND unapproved changes to the production environment.

   Please advise. Thank you.

   This step is often skipped when I click on Next from Step 1. The Deployment Wizard will skip straight to '4 - Review Deployment Script'. This behavior is inconsistent: sometimes '3 - Review Dependencies' IS enforced even though it is skipped and other times it is not. In our situation, the rule is to NOT enforce dependency changes.

   This has bitten me several times in the past, so I now always click on Back when on Step 4 to see if Step 3 was enforced or not. Of three deployments today requiring SQL Commpare, two of them exhibited this behavior.… more

   4 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 →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  Michelle Taylor responded

   We’ve seen this behaviour occasionally and believe we have fixed the problem in 10.7 – could you try upgrading, and email support@red-gate.com if you are still experiencing this problem?

6. Don't offer upgrades that remove your license.

   Don't offer upgrades that remove your license. I have a licensed version of the product, it asked me to upgrade and now it's asking me to enter my serial number. I didn't realize that the upgrade would take away my licence. I want my original licence back, these kind of ninja money grabs are just plain awful.

   5 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  ·  1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. 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 →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   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.

8. 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 →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   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.

9. Make sure the connections are valid before getting all the objects from the first server.

   I have a server that I have to change the password on a lot, and can never (rarely) remember if I have changed the compare tool for the new password. I guess I could switch the servers around so that was the first it tries to get objects from. BUT it would be a nice feature to have it fail before doing any actual work.

   7 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 →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  AdminDavid Eadie (Software Engineer, Redgate) responded

   Hi,

   In SQL Compare 12 we have changed the comparison workflow so that we register both databases in parallel. This will allow the comparison to show you errors connecting to your target database before all the objects in the source have been registered.

10. allow exclude if object name begins with underscore (_)

    In previous versions of sql compare you were able to use the underscore character as part of your filters (exclude if object name begins with _)

    This no longer works and as underscores are fairly common when creating sample objects (at least in my company this makes it impossible for us to use.

    6 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 →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  AdminMichael Upton (Development Lead, Redgate) responded

    This problem has been fixed in version 11.2 (currently only available via frequent updates). We have added new ‘Like’ and ‘Not like’ filter match operators which honour all SQL LIKE wildcards, and changed the previous ‘Begins with’, ‘Ends with’, and ‘Contains’ to stop treating them as wildcards.

    You may need to edit existing filters to take advantage of the new behaviour.

11. 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 →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Select source/select target + drag and drop removed - integration is now very poor

    Along the lines of this post: http://redgate.uservoice.com/forums/141379-sql-compare-feature-suggestions/suggestions/2893526-the-integration-into-ssms-is-far-worse-then-previo
    Before we could right click and choose a database to be the source or the target of the comparison. Now I find myself having to choose the target as the source then press switch and then choose another source using the "compre to" option - it's quite a step backward from the previous integration.

    7 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 →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  AdminMichael Upton (Development Lead, Redgate) responded

    Sorry this has taken so long for us to update, but based on your feedback we reinstated the full SSMS integration back in SQL Compare version 10.2.

13. In project options, add option to Ignore 'With Encryption' statement
    7 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 →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  Michelle Taylor responded

    An option is available to ignore With Encryption in the latest version.

14. The integration into SSMS is far worse then previous versions, bring back Drag and Drop

    The integration into SSMS is far worse then previous version. Prior versions allowed selecting the second DB for the comparision by dragging onto the search pane from the object explorer. This took care of selection and login. Now we have to select the server, database and login as descreet tasks instead of just dropping and dragging. This was not an improvement.

    4 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 →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  AdminMichael Upton (Development Lead, Redgate) responded

    Sorry it’s taken so long to update this, but we reinstated the old SSMS integration based on your feedback back in version 10.2.

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 →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    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. Double click in project window.

    When in the project window (showing you your recent projects you have loaded) it would be nice if you could just double click on an item to get it to load. Currently you have to click on a line to highlight it, then double click on it to load. It would be very nice if you didn't require the highlight step and part of the double-click would also highlight and open the item clicked on.

    3 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 →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  AdminMark Jordan (Software Engineer, Redgate) responded

    I’ve just had a look and this seems to be fixed in the v12 version of the project window, available in 12.0.40: see https://forums.red-gate.com/viewtopic.php?f=200&t=80430 for more details

17. 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 →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    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.

18. Open script with SSMS2012, there is no option yet?

    There is no option to choose to open with ssms2012 in the dialog that is shown for deployment, i can choose ssms2008 but not 2012. Is this available somewhere?

    8 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 →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  AdminMichael Upton (Development Lead, Redgate) responded

    Support for SSMS 2012 was added in version 10. Version 11 has added support for SSMS 2014.

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 →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  AdminDavid Eadie (Software Engineer, Redgate) responded

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

20. CREATE QUEUE [dbo].[Applicati

    Support the POISONMESSAGEHANDLING argument for service broker queues.

    /****** Object: ServiceQueue [dbo].[ApplicationLogSendingQueue] Script Date: 03/15/2012 11:34:56 ******/
    CREATE QUEUE [dbo].[ApplicationLogSendingQueue]
    WITH
    STATUS = ON ,
    RETENTION = OFF ,
    POISONMESSAGEHANDLING (STATUS = OFF) ON [PRIMARY]
    GO

    5 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 →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  AdminDavid Eadie (Software Engineer, Redgate) responded

    The latest release of SQL Compare contains support for this syntax.