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. Agent jobs

    Would be great if SQL Server Agent jobs could be incorporated into SVN

    473 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    30 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Make SQL Data Easier to Merge

    Currently, SQL Data files contain a bunch of insert statements, but the order of the insert statements can be inconsistent. For example, new records might get inserted on the top or the bottom. Also, multiple SET IDENTITY_INSERT statements sometimes get created. This makes it difficuly to merge data changes between multiple branches in TFS Source Control. If the Insert statements had a consistent order and only included one SET IDENTITY_INSERT diffs and merges would be easier.

    420 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    22 comments  ·  Static Data  ·  Flag idea as inappropriate…  ·  Admin →
  3. SQL Source Control Static Views (or Table Subsets using WHERE clause)

    I would like the ability to source control a subset of a table (perhaps using a view).

    I have inherited a database where lookup data is intermixed with user defined data. We reference the lookup data in the table using a code (VARCHAR) that is unique when another field is NULL, so it is possible to ensure that records are created/updated/deleted without concern for the primary key involved.

    For more information, you can refer to this forum post:
    http://www.red-gate.com/messageboard/viewtopic.php?p=50087

    359 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Static Data  ·  Flag idea as inappropriate…  ·  Admin →
  4. Allow me to specify a subset of columns for static data like I can in SQL Data Compare

    I do not want to source control certain columns in my reference tables (e.g., update date/times since these are different on each server and get set by a DEFAULT).

    312 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Static Data  ·  Flag idea as inappropriate…  ·  Admin →
  5. Command line tool (or API) for SQL Source Control Integration

    We have an automated system for building our developer environments. It would be nice to have a command line tool that we can use as part of the machine build script to pull down the latest version of the database, build the initial database and link that database back to the TFS source. Our platform consists of quite a large number of databases so linking to them all manually via the UI is a bit tedious.

    264 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    23 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Support different static data per customer

    I have a single schema for all customers but different reference data for different customers. It would be nice if I could manage this all within SQL Source Control. This should also be understood by SQL Compare and my continuous integration system when it comes time to deploy this to my different environments and customers' sites.

    254 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Static Data  ·  Flag idea as inappropriate…  ·  Admin →
  7. Ability to shelve items in TFS.

    TFS lets the user "shelve" items before checking them in. A way to save them while they are still inprocess or not code reveiwed yet. It would be nice if SQL Source Control let us shelve the items instead of checking it in - with the same functionality we get when shelving through Source Control Explorer in Visual Studio.

    214 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    16 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Work with a Visual Studio Database Project

    Can this work if I already have a VS Database project setup? Meaning can this work and interact with a VS Database project so that I can continue working on the actual db in SSMS, but the files get saved to the VS Db Project?

    210 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    36 comments  ·  Flag idea as inappropriate…  ·  Admin →

    This is now available in the full release of SQL Source Control, http://www.red-gate.com/products/sql-development/sql-source-control, but it is still a beta feature.

    SQL Source Control can link databases to the most recent version of Microsoft database projects (those folders containing a .sqlproj file).

    It’s important to stress that this is a beta-quality feature, and as such it is only intended for experimental use. In particular, we are aware of some limitations regarding database-level extended properties, permissions and CLR assemblies. If you encounter these limitations or any other problems with this new SSDT compatibility, please let us know by using the Feedback link in SQL Source Control or contacting support@red-gate.com.

  9. Work with multiple databases at a time

    Why not offer a "SQL Source Control" entry in the right-click menu for the instance itself, so that I can look through/update/commit changes to/from several databases at once? Why do I have to specify a separate link for each database I'm interested in? Starting at the instance level would allow me to not only find *all* changes, it would also permit tracking objects within the instance but outside any database, such as "Security/Logins", "Security/Server Roles", "SQL Server Agent/Jobs", "Server Objects/Endpoints", and "Server Objects/Linked Servers".

    203 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Undo data changes

    I can undo any DDL operation but I don't have the option to undo a data change in a source controlled table. I think data changes should also be in the list of changes I can undo.

    200 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Static Data  ·  Flag idea as inappropriate…  ·  Admin →
  11. Get specific version from source control (SVN: Update to revision)

    Instead of Get Latest, I want to be able to get a specific version out of source control and reapply it to the database. This would allow me to rollback changes that were accidentally committed. I should be able to specify what version/revision that I want to go back to.

    This is the same as getting a previous version from source control so that I can debug an issue a user found in a previous release.

    185 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Elizabeth Ayer responded

    We are considering this feature as a candidate for SQL Source Control 5.

    You can still work around this by using SQL Source Control with SQL Compare Pro. Just highlight the specific version in the history that you want and click the “Update to this version using SQL Compare Pro” button.

    A free trial of SQL Compare Pro is available at http://www.red-gate.com/products/SQL_Compare.

    The SSMS Integration Pack, which comes with SQL Compare Pro also allows you to deploy directly from SQL Source Control repositories.

  12. initial setup automation

    We've got HUNDREDS of databases. Dozens in active development.
    Several obvious details are missing from the initial setup of a linked database. These are specific to VSS, but I'm sure apply to other SSC versions:
    1) Remember the last used (VSS) Database path.
    2) Remember the last Source Control Folder, BUT... SUGGEST the name of the new DB as the terminal project name.
    3) Add a Check box to "Auto Commit" ALL objects.

    The amount of retyping (or even copy/paste/edit) the same information over and over is quite annoying.

    159 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    32 comments  ·  Initial Setup  ·  Flag idea as inappropriate…  ·  Admin →

    I wanted to update this as some recent testing has shown we broke the workaround for this a while ago. We are however scoping out what it’d look like to solve this properly. We have many of your contact details, so will be reaching out to a few of you for help, but if you’re super keen to get involved feel free to post above or email me and we’ll get you involved.

  13. Support Azure Active Directory Authentication

    This has over 50 votes but its in SQL Prompt. This is a HUGE pain for us as we need to use AD to adhere to security policy.
    https://redgate.uservoice.com/forums/94413-sql-prompt/suggestions/15008409-add-support-for-azure-active-directory-authenticat

    150 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Azure  ·  Flag idea as inappropriate…  ·  Admin →
  14. Database Diagrams

    Support to check-in database diagrams

    149 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add ability to associate check ins with Work Items in TFS

    Visual Studio already allows this which keeps track of which Source Control items go with which Change Control items. This would also be greatly beneficial if we could associate the database changes as well.

    133 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    30 comments  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Elizabeth Ayer responded

    Hi – this request was closed when the ‘TFS work items’ feature was released. http://documentation.red-gate.com/display/SOC3/Committing+changes

    However, we’re still hearing about this enough that I’d agree with commenter Ben: it should be reopened.

    We will continue to gauge interest here on UserVoice. Please do tell us more in the comments about what you expect to be able to do with Work Items in SQL Source Control.

  16. Support TFS Gated Checkins

    We desperately need the ability to supported gated check-ins so breaking changes do not get into source control.

    132 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Foreign keys recreated with NOCHECK during data sync

    We have the same issue as noted here: http://www.red-gate.com/messageboard/viewtopic.php?t=13662&highlight=foriegn+foreign+key

    The FK is recreated with NOCHECK during data sync which triggers a schema change.

    104 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Static Data  ·  Flag idea as inappropriate…  ·  Admin →
  18. Migration Script Rollbacks

    The only obstacle I have with switching to SQL Source Control 3 as a complete solution to source controlling and deploying is its inability to rollback custom code in a Migration Script. I would like when creating a Migration Script the ability to create a Reverse Migration Script so that if I use SQL compare to roll a code push back to a previous version in source control, it will grab the reverse script the same way as it grabs the migration script currently when pushing.

    For example, if my migration script has an update statement in it to modify…

    92 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Keep Static Data Stored in PK Order

    When storing the data items in files, it would be good to keep everything in PK order so that changes are easier to spot. Historical order is less important when working with static data.

    90 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Support SVN "Id" keyword

    We already maintain our database scripts in SVN (using Tortoise), and are very keen to change over to your product.

    We include the SVN keyword $Id$ in a comment at the top of every object file. When we commit, SVN automatically updates this to provide the Date, Author and Revision number of the last commit. This means that we're easily able to see which version of a particular stored procedure or function is in a client's database.

    SQL Source Control doesn't like this though. When I commit a change through SQL Source Control, the Id is updated by SVN, and…

    89 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Flag idea as inappropriate…  ·  Admin →

    We’re currently not planning to support this for v1. Would you be ok to remove the $id$ keyword for now?

    We’ll have to see how many votes this suggestion gets…

    Internal reference number: SOC-113

← Previous 1 3 4 5 28 29
  • Don't see your idea?

Feedback and Knowledge Base