270 results found

1. Let SQL Compare adopt the Comparison Options of Source Control Source

   Unfortunately SQL Compare does not adopt the Comparison Options specified by the Source (here git repository created by SQL Source Control) which are saved in "ComparisonOptions.xml" in the git repository. Instead in SQL Compare I have to click on "Edit project" -> "Options" and check again "Ignore users' permissions and role memberships". This feels somehow not intuitive. During setup of the SQL Compare project a checkbox "adopt comparison options from source" would be nice - or maybe an "adopt" button just after setup.

   I saved the SQL Compare project as an .scp file which in fact is an XML file. I see that the comparison option "IgnoreUsers" is saved inside the XML document under /Project/Options. So of course SQL Source Control and SQL Compare are 2 different products but they share alot, e.g. the comparison option dialog. Unfortunately they share not the saved configuration of the comparison option.

   Unfortunately SQL Compare does not adopt the Comparison Options specified by the Source (here git repository created by SQL Source Control) which are saved in "ComparisonOptions.xml" in the git repository. Instead in SQL Compare I have to click on "Edit project" -> "Options" and check again "Ignore users' permissions and role memberships". This feels somehow not intuitive. During setup of the SQL Compare project a checkbox "adopt comparison options from source" would be nice - or maybe an "adopt" button just after setup.

   I saved the SQL Compare project as an .scp file which in fact is an XML file.… more

   12 votes

   Vote 0 votes 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

   Submit Rating

2. 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:

   1. Don't want to use the /include:Identical switch
   2. If the two databases are identical, then the error reported on the console should be suppressed (using some switch)
   3. The html file should contain only the summary (say 29 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:

   1. Don't want to use the /include:Identical switch
   2. If… more
   12 votes

   Vote 0 votes 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

   Submit Rating

3. 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, saSQL01prod has dbDataReader in the [db1] database. saSQL01test does not. We want SQL Compare to generate a script to apply the PROD permissions but using the TEST user account and end up with the saSQL01test user having the same permissions to the [db1] database in TEST as the saSQL01prod user has in PROD.

   Clear as mud???

   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… more

   12 votes

   Vote 0 votes 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

   Submit Rating

4. In SQL Compare, have "SQL Prompt view tab" with SQL Prompt Professional licence, not just the SQL Toolbelt licence

   We want to use the SQL Prompt view tab in SQL Compare, but you apparently specifically need the SQL Toolbelt or SQL Toolbelt Essential licence.

   We don't have SQL Toolbelt (anymore), but we have both Redgate Deploy and SQL Prompt Professional, and i believe we also have all the tools shipped with SQL Toolbelt.

   Can't this tab also be made available for people using Redgate Deploy and/or SQL Prompt Professional, as we have all the tools/software of the Toolbelt already (i guess), but the bundle is named different...?

   12 votes

   Vote 0 votes 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…)
   under review  ·  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

   Submit Rating

5. Allow Connections to Microsoft Fabric SQL Databases

   I would love to be able to use the tools I know and love to access Microsoft Fabric SQL Databases.

   Currently when connecting to Fabric SQL Databases the following error is displayed: "Fabric is not currently supported."

   I ask that Fabric be supported by all products in the SQL Toolbelt, but specifically, SQL Prompt, SQL Compare and SQL Data Compare.

   11 votes

   Vote 0 votes 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

   Submit Rating

6. Pull filter from source controlled database

   When comparing a source controlled database (SSC) to a live database, it would make sense to use the source controlled database's object filter (filter.scpf file) when running the comparison instead of having to manually recreate the filter inside of the SCP project. Also, it would be better if the SCP project stored a link to the filter file used instead of storing the filter string, as it is very inconvenient to have to maintain these separately. If the filter file is changed in SSC, I want SCP to be able to pick up the change automatically.

   11 votes

   Vote 0 votes 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…)
   under review  ·  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

   Submit Rating

7. Sync a Database to a Source Control Repository

   We really need the ability to "sync" a database to VCS repository, not just compare. I know this limitation exists by design because conflicts can be missed, but we have a scenario that demands it. We have batch check-ins that can take up to a half a day to commit manually.

   10 votes

   Vote 0 votes 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

   Submit Rating

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

   Vote 0 votes 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

   Submit Rating

9. CSV should use entirely empty value (no "") for null

   Current behaviour: the CSV file represents null as the 8-character string “<NULL>” . e.g. If I have a table with an integer primary key column id, a varchar column a, and a varchar column b, and the table has one newly-inserted row (1, NULL, “asdf”), the CSV file would look like this:

   o “Type”,”idk”,”as”,”at”,”bs”,”b_t”
   o “In1”,”1”,”<NULL>”,””,”asdf”,””

   Desired behaviour: allow the CSV file to represent null as a completely empty entry. E.g. the CSV file would look like this:

   o “Type”,”idk”,”as”,”at”,”bs”,”b_t”
   o “In1”,”1” ,, ””,”asdf”,””

   Suggested options:

   1) Command line switch toggling between “<NULL>” and empty string
   2) Allow users to define how to represent null in the UI

   Current behaviour: the CSV file represents null as the 8-character string “<NULL>” . e.g. If I have a table with an integer primary key column id, a varchar column a, and a varchar column b, and the table has one newly-inserted row (1, NULL, “asdf”), the CSV file would look like this:

   o “Type”,”idk”,”as”,”at”,”bs”,”b_t”
   o “In1”,”1”,”<NULL>”,””,”asdf”,””

   Desired behaviour: allow the CSV file to represent null as a completely empty entry. E.g. the CSV file would look like this:

   o “Type”,”idk”,”as”,”at”,”bs”,”b_t”
   o “In1”,”1” ,, ””,”asdf”,””

   Suggested options:

   1) Command line switch toggling between… more

   10 votes

   Vote 0 votes 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

   Submit Rating

10. Always trust server certificate via option

    Version 15 adds checkboxes for Encryption and to Trust a server certificate, but if you don't maintain proper certificates you now always need to check the Trust server certificate box on both servers for new comparisons. It would be great if there was an option to default the behavior of these checkboxes to fit your environment.

    10 votes

    Vote 0 votes 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

    Submit Rating

11. Allow SQL Compare to ignore difference due to ALTER and CREATE

    When comparing a VS 2012 database project to a database, when the only difference is ALTER vs. CREATE (which happens because a stored procedure ALTER was executed directly, then saved) the comparison fails. An option to ignore this difference would be very handy.

    9 votes

    Vote 0 votes 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

    Submit Rating

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

    Vote 0 votes 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

    Submit Rating

13. Install updates for all products at once

    I'm using the Update software feature directly from the application. we have 3 products licensed, and i have to run all 3 updates separetely. i would be nice to install all 3 products with one setup run.

    9 votes

    Vote 0 votes 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

    Submit Rating

14. Ignore datatypes

    I created a new database based on an existing but replaced all datetime columns by datetime2(2) and do not want to show this as difference neither want it be rolled back, when I create deployment scripts.

    Same could happen, if I change the size of a varchar, decimal or integer datatypes (bigint <> int <> smallint ...) and even, if a number is in one database is stored in a varchar field, I could want to ignore this and deploy only everything else

    See also
    https://redgate.uservoice.com/forums/141379-sql-compare/suggestions/7109654-an-ignore-option-for-differences-between-varchar
    which suggests to ignore varchar vs. nvarchar

    BTW: I solved my problem by syncing the source database with an empty script folder, used Notepad++ to replace all [datetime] by [datetime2] and finally compared the script folder with the target database.

    I created a new database based on an existing but replaced all datetime columns by datetime2(2) and do not want to show this as difference neither want it be rolled back, when I create deployment scripts.

    Same could happen, if I change the size of a varchar, decimal or integer datatypes (bigint <> int <> smallint ...) and even, if a number is in one database is stored in a varchar field, I could want to ignore this and deploy only everything else

    See also
    https://redgate.uservoice.com/forums/141379-sql-compare/suggestions/7109654-an-ignore-option-for-differences-between-varchar
    which suggests to ignore varchar vs. nvarchar

    BTW: I solved my problem by syncing… more

    9 votes

    Vote 0 votes 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

    Submit Rating

15. Add an option to the behavior section to include SORT_IN_TEMPDB = ON on all of the CREATE INDEX statements.

    For those of us working with data warehouses, using SORTINTEMPDB is the default behavior we need.

    9 votes

    Vote 0 votes 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

    Submit Rating

16. Add an option to ignore seed value when scripting sequences.

    There is an option to ignore identity seed values but none for sequence seed values.

    9 votes

    Vote 0 votes 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

    Submit Rating

17. Autofill fields for "Create new snapshot" using the other database selected

    The source for create new snapshot defaults to database. Automatically populate Server, Authentication, Database and New Snapshot name using the Database information on the other side of the compare window.

    Customizable name tags for the new snapshot name would be perfect: [SERVER][DATABASE][DATETIME].snp

    9 votes

    Vote 0 votes 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

    Submit Rating

18. Compare against Database Projects

    It would be great to see SQL Compare support Visual Studio Database Projects (.sqlproj).

    Current if you choose Source Control | Scripts, you can point to the project folder, but then SQL Compare gets confused because it loads in extra .sql files (eg. the 'create database'.sql that gets put in the build output 'bin' folder).

    Selecting the 'Tables' sub-folder works more reliably (if just comparing tables!), but then pushing changes down to the files results in schema that no longer compiles because the SSDT tools require 'GO' separators between each DDL statement.

    8 votes

    Vote 0 votes 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

    Submit Rating

19. filter

    In SQL Compare make it remember the filter you last choose.

    I set up my filters and saved them to a file. Then picked that file in the filter drop down.

    The next time I bring up SQL Compare, I have to pick the filter again from the drop down. SQL Compare should remember the last one I used. Or give me the option to remember it like The Project Options allow you to save as My Defaults.

    8 votes

    Vote 0 votes 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

    Submit Rating

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

    Vote 0 votes 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

    Submit Rating