SQL Source Control

Welcome to the SQL Source Control feature suggestion list. Find out more information about SQL Source Control at http://www.red-gate.com/products/sql-development/sql-source-control/.

If you have any questions, need help or have found a bug in SQL Source Control, please review our support information http://redgatesupport.red-gate.com/home.

To get new features, performance improvements and bug fixes as soon as they’re available, you may want to turn on frequent updates: http://www.red-gate.com/products/sql-development/sql-source-control/frequent-updates

How can we improve SQL Source Control?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Keeping history of locked and unlocked objects

    Locking feature doesn't keep history of who has locked or unlocked specific objects in database. This could become useful when a person unlocks an object locked not by him/her and would help to track historical changes.

    It would require very few changes - additional history table,

    [SQLSourceControl].[LockObject] and [SQLSourceControl].[UnlockObject] procedures would have to be modified.

    Possibly an additional view to see that data in SQL Source Control instead of selecting raw tables.

    2 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  History/Log  ·  Flag idea as inappropriate…  ·  Admin →
    • Use JSON as a data source

      from http://country.io/continent.json you can have both countries to contenents and give Countries valid cities eg http://country.io/capital.json Which means if you can defined a key-value pair you can create more accurtate test data that placing "St Petersburg" in "Iceland" which is the current option.
      At worse if the json file was downloaded and 'mounted' as a table would be useful. But really JSON is the new datasource that Red-gate has to connect to.

      3 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        0 comments  ·  Flag idea as inappropriate…  ·  Admin →
      • Connections to server

        With Amazon RDS, the server names are changed each time an instance is created. If a dev instance is recreated monthly, and a testing instance is recreated daily, it is impossible to keep the connection to source control when the server names change.

        The only way to get source control to work with our system is if it were able to connect to a static end point (dns record) rather than the server name itself

        3 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          0 comments  ·  Initial Setup  ·  Flag idea as inappropriate…  ·  Admin →
        • Source Control Standalone instead of SSMS snapin

          Source conrtol should be a standalone app not SSMS addin. When performing get latest or commits, on large environments and slow connections this can easily take 20 minutes during which a click anywhere else in SSMS restarts the get latest/commit process. The logical use of source control being a SSMS addon has been outlived.

          5 votes
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            1 comment  ·  Better Support for Shared Db Dev Model  ·  Flag idea as inappropriate…  ·  Admin →
          • SQL Compare and SQL Data Compare Deployment Script - Static Name

            When using either SQL Compare or Data Compare, during deployment, can we have an option to supply and store a static name for the script file rather than having to overwrite script file name in each deployment. You could supply an option to automatically overwrite the file. For early development I want one script only, I don't need to maintain a history, especially if I'm going through the deployment testing phase.

            1 vote
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              I agree to the terms of service
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              1 comment  ·  Flag idea as inappropriate…  ·  Admin →
            • SQL Toolbelt Installation/Product Manager - Control Panel

              It would be great if we could have a product manager for SQL Toolbelt and or individual products we're licensed for. In the manager you could see which products you have access to, which ones that are installed, view the VS and SSMS versions installed in your local system and install/uninstall products to the VS and SSMS versions. This would be similar in operation to the Telerik Control Panel which provides this kind of functionality.

              6 votes
              Vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                I agree to the terms of service
                Signed in as (Sign out)
                You have left! (?) (thinking…)
                0 comments  ·  Flag idea as inappropriate…  ·  Admin →
              • Creating database from scratch on linux

                I have a bunch of Ruby services which talk to sql server. I'd love to be able to stand up and tear down databases for development using Microsoft's mssql-server-linux docker container while still managing my database via Redgate. This would require a linux-based CLI tool that could create the database from source.

                To do this would require a linux-compatible container

                1 vote
                Vote
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  I agree to the terms of service
                  Signed in as (Sign out)
                  You have left! (?) (thinking…)
                  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
                • View Uncommitted Changes

                  I like how SQL Source Control can show you that there is an uncommitted change to an object with a blue dot on the object. Could this be built upon by allowing users to right click on the object and then have an option there to show a diff between the current code and what is committed to source control? This would be the same results that you see when you go to the 'Commit' tab and select an uncommitted object. It would be very helpful to see that comparison easily.

                  3 votes
                  Vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    I agree to the terms of service
                    Signed in as (Sign out)
                    You have left! (?) (thinking…)
                    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
                  • Allow changes to comments in code to be committed

                    SQL Source Control doesn't recognise changes to objects when the only change that has been made is in comments. The change is marked in object explorer when initially made, but clicking refresh in the source control window then ignores the change and removes the indication that the object has changed. There doesn't appear to be any setting to remove this filtration. The only other option is to alter the object's functionality or definition, commit, then change the definition back and re-commit. This is inherently risky, and should be unnecessary.

                    We use comments as a key part of our system documentation,…

                    1 vote
                    Vote
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      I agree to the terms of service
                      Signed in as (Sign out)
                      You have left! (?) (thinking…)
                      2 comments  ·  Flag idea as inappropriate…  ·  Admin →
                    • Hide columns for System Version Tables

                      We are using System Versioned Tables, and on these tables SQL server adds 2 new columns SysStartTime and SysEndTime. These columns are typically marked as hidden and we need a way to ignore comparison for these. Either by a column level filter, or an option to ignore system versioning columns

                      1 vote
                      Vote
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        I agree to the terms of service
                        Signed in as (Sign out)
                        You have left! (?) (thinking…)
                        0 comments  ·  Static Data  ·  Flag idea as inappropriate…  ·  Admin →
                      • Display the server name in the "SQL Source Control" Setup window.

                        Someone in my team linked one of our test environment's databases to his source control. He was in a feature branch and just performed a "Get Latest" on the dB..... Now we have to reimplement the integrated changes. Please display the Server name in the setup window to avoid confusion and make sure this is clear.

                        8 votes
                        Vote
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          I agree to the terms of service
                          Signed in as (Sign out)
                          You have left! (?) (thinking…)
                          3 comments  ·  Initial Setup  ·  Flag idea as inappropriate…  ·  Admin →
                        • ReadyRoll integration with Source Control

                          ReadyRoll looks great but one of it's downsides is that you have to use Visual Studio. If mostly work gets done using SSMS, then switching to Visual Studio is not a great experience.

                          Both ReadyRoll and SQL Source Control use the same comparison engines, they both output objects as files on disk and support migrations.

                          To satisfy both worlds (making great experience when using Source Control on SSMS) and have a proper way to automatically update databases from source control files using migrations (like ReadyRoll does), SQL Source control should integrate with ReadyRoll - after each commit, a migration script…

                          21 votes
                          Vote
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            I agree to the terms of service
                            Signed in as (Sign out)
                            You have left! (?) (thinking…)
                            3 comments  ·  Flag idea as inappropriate…  ·  Admin →
                          • Produce a warning when a JOIN's ON clause does not reference the joined table

                            During a data-refactoring effort, I accidentally created a query that looked like this:

                            SELECT *
                            FROM Customers
                            JOIN Orders o ON o.CustomerId = o.CustomerId

                            Obviously, this is wrong, and results in a cross join. It would be great if SQL Prompt could produce a warning when:
                            1. ON clause compares a column to itself
                            2. ON clause does not reference the table being joined to

                            4 votes
                            Vote
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              I agree to the terms of service
                              Signed in as (Sign out)
                              You have left! (?) (thinking…)
                              1 comment  ·  Flag idea as inappropriate…  ·  Admin →
                            • Selections in Commit tab remain selected in Undo Change dialog

                              In the commit tab you can see the differences between source control and the database which makes it great for deciding what you want to commit or rollback. If you select items in this tab and them right click and undo changes your selections are lost and you have to re-select in the Undo Changes dialog which doesn't let you see the change.

                              As a developer I want to be able to see the change that I am about to undo.

                              1 vote
                              Vote
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                I agree to the terms of service
                                Signed in as (Sign out)
                                You have left! (?) (thinking…)
                              • Unable to connect to the Redgate Client Service.

                                'Please ensure that the service is started. Click here for more information about this problem.'
                                How about fixing this bug for when source control have forgotton its lic, which of course is fine . you can then try deactivating and reactivating, it says its is ok but nothing has changed. Would be so nice to be able to log on to your subscription, and tell it 'USE THIS ONE' so it can see on a redgate site what lic to use.

                                10 votes
                                Vote
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  I agree to the terms of service
                                  Signed in as (Sign out)
                                  You have left! (?) (thinking…)
                                  1 comment  ·  Initial Setup  ·  Flag idea as inappropriate…  ·  Admin →
                                • Find revision number of deployed database

                                  It would be very useful if it was possible to see which revision number was last deployed to a database. Source Control 4 used to update the extended properties after deployment but version 5 no longer does this.

                                  Not knowing the revision number makes it difficult to bring a Live db up to the same revision as a UAT db, and ensuring the required migration scripts also get executed on the Live db.

                                  Any change this could be added somewhere? Extended properties seemed a good place to save it.

                                  9 votes
                                  Vote
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    I agree to the terms of service
                                    Signed in as (Sign out)
                                    You have left! (?) (thinking…)
                                    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
                                  • Remove operations prior to a CREATE statement when linking to .sqlproj files

                                    I'm linking to an existing database using a local folder. The database is linked in shared mode.

                                    The local folder was built by SSDT and contains a .sqlproj file. I'm notified of the beta functionality when linking, so I know SQL Source Control identifies the project as linking to SSDT.

                                    When I add a stored procedure, the resulting script starts with:
                                    SET QUOTED_IDENTIFIER ON
                                    GO
                                    SET ANSI_NULLS ON
                                    GO

                                    These statements don't compile in SSDT. The first statement in each script must be a create statement.

                                    I had removed these lines from the statement that I ran against SQL Server…

                                    4 votes
                                    Vote
                                    Sign in
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      I agree to the terms of service
                                      Signed in as (Sign out)
                                      You have left! (?) (thinking…)
                                    • SQL Source Control Missing in SSMS in SQL2016

                                      When I installed Toolbelt I has SQL 2014 now I have added SSMS2016 and its only Prompt and SQL Test that is visible. I have tried running a reinstall but it tells me that the products are already installed - what's going on!

                                      4 votes
                                      Vote
                                      Sign in
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        I agree to the terms of service
                                        Signed in as (Sign out)
                                        You have left! (?) (thinking…)
                                      • Add a "rerun" option for edited migration scripts

                                        Currently there is an option to edit migration scripts however edits will not get applied to other environments if the old version of the script was already run.

                                        Imagine the scenario where a migration script is created to update one record in a table that does not have it's data versioned. The script is checked in and deployed to the CI environment and the QA (test) environment. QA test finds that the update was incorrect. Development edits the migration script to correct it. The edited script will not get run again on those environments.

                                        Currently there are only two work…

                                        4 votes
                                        Vote
                                        Sign in
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          I agree to the terms of service
                                          Signed in as (Sign out)
                                          You have left! (?) (thinking…)
                                          0 comments  ·  Flag idea as inappropriate…  ·  Admin →
                                        • Make it easier to recover when SQL Source Control generates incorrect AutomaticSchemaChange.patch

                                          When using V3 of migrations, SQL Source control parses the migration script, finds all dependent objects, and makes sure that the AutomaticSchemaChange.patch file brings the database up to a state where the user-written migration script can run. But, sometimes the AutomaticSchemaChange.patch file has a bug in it, due to a bug in the SQL Compare engine. I can file a bug on this, but those bugs don't seem to get fixed very quickly, and without a fix I can't deploy my database.

                                          The only workaround that I've found in this case is to manually edit the AutomaticSchemaChange.patch file to fix…

                                          4 votes
                                          Vote
                                          Sign in
                                          Check!
                                          (thinking…)
                                          Reset
                                          or sign in with
                                          • facebook
                                          • google
                                            Password icon
                                            I agree to the terms of service
                                            Signed in as (Sign out)
                                            You have left! (?) (thinking…)
                                            0 comments  ·  Flag idea as inappropriate…  ·  Admin →
                                          • Don't see your idea?

                                          Feedback and Knowledge Base