Skip to content

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

SQL Source Control

Categories

JUMP TO ANOTHER FORUM

(thinking…)

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

588 results found

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

    189 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    10 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

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

    135 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    30 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    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.

  3. Selective XML Indexes

    Correctly support SQL Server 2012 Selective XML Indexes (SXI). Currently any SXIs are committed to source control as Primary XML indexes

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  4. Bug message -- An inconsistancy was detected during an internal operation in database . . .

    Got an error message running a data compare:

    Bug message -- An inconsistancy was detected during an internal operation in database 'DWC' (ID:5) on page (1:3531152). Please contact technical support. Reference number 7.

    When I tried to find a link in the program to technical support, best match I saw took me here. Maybe you need a better link or even a "Contact Support" button which pasted the text of the message into an e-mail or something along those lines?

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  5. mark a migration script as "post" code deploy, generate release scripts FOR and EXCLUDING "post" code migrations

    We have to carefully create schema release scripts and coordinate them with code deploys in order to maintain compatibility, so we often have "pre" and "post" schema scripts. The "pre" scripts are run before code, and the "post" scripts are run after code.

    In our cases, the 'post' deploy scripts are generally just cleanup of schema, removal of things that are no longer referenced by the code. This includes removal of any "backward compatibility" that is no longer needed. It could be dropping tables or columns, or removal of a column from the SELECT output of a stored procedure.

    Currently…

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  6. Integrate Source Control Explorer

    Similar to the Object Explorer pane in SMSS, integrate the Source Control Explorer from TFS. This way, it isn't necessary to also have Visual Studio open to navigate branches, create new folder on the fly, etc...

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  7. Detail the SQL roles required for SQL Source Control needs to commit code

    Provide details

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Better Support for Shared Db Dev Model  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  8. Database name flickering in Object Explorer

    Version 3.5.3.29
    SSMS 2008 Express, connected to local 2005 Express instance, running on Windows 7 as a guest within VMWare Workstation.

    As standard I have all my databases offline, and bring them online individual as and when required.

    The database name in the Object Explorer shows the "spinning" white and blue dot - but is constantly flickering/flashing. It will do this until the "Commit changes" or "Get latest" tab has been viewed... even if the Source Control screen is not even open (let alone having focus).

    The only way to stop it is to open SQL Source Control and refresh…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  9. Create a 'Mixed' model in addition to 'Shared' and 'Dedicated'

    We generally share one database, but occasionally our developers keep a local version. All of these point to source control, which we consider the 'official' version of the database. A developer could commit changes to source control from their dedicated database. They could even edit the code manually.

    However, if we set up the shared database under the 'shared' model, we can't get latest from source control.

    We currently work around it by setting every database as 'dedicated', even the shared database, but then we miss out on keeping track of which users made which modifications.

    Please offer a 'Mixed'…

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Better Support for Shared Db Dev Model  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  10. 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".

    215 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    8 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  11. initial checkout failure not cought

    I was checking out a database that contained changes. (new machine, database restored from backup)

    The initial checkout from SVN failed because of a network issue. However the UI did not report that failure and instead proceeded to compare my current database to the local broken working copy.

    It seems that the code executing the checkout is wrapped in an exception eating try catch block.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Initial Setup  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  12. I just want to add, query by query, to track changes. When i commit a query, the whole damn DB of queries (1000+) loads. Too cumbersome.

    New user, I just want to add a query as I develop, to track changes. I expect to 1) Add a query to source control. 2) Commit the query 3) Track changes........ Problem is, every time I commit the query, the entire DB stored procedures load into memory, slow and not working for me.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Initial Setup  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  13. Migrated to new SVN server, timeout on existing linked databases is way too long

    We moved our SVN repositories to a new server and the old server is already gone. I then moved ahead and tried to unlink my existing databases so I can link them to new server address (svn relocate would be another option)... Problem is that sql source control is now trying to connect to the old server and the unlink dialog is just sitting there for minutes, and I'm getting "Visual Studio is busy...." messages

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Initial Setup  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  14. Default Check-in Comments

    It should be possible to configure default check-in comments for setting up WorkItem-Codes. We got one specific work item for database changes. So a developer doesn't need to type the code manually or has select it from previous check-ins.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  15. Make it obvious if there any "Get latest" items

    When the SQL Source Control tab refreshes, it would be exceedingly useful to see if there are any items under the "Get latest" tab without having to go into the tab.

    I would suggest adding the number of changes in the tab to the tab title. For example...

    _/ Commit changes (12) _/ Get latest (2) _.....

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  16. Automatically commit changes as they are made

    It would be nice to be able to automatically commit changes in the background when an object is created or modified.

    19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  17. Last update produces massive load and timeouts!

    The last update (current version: 3.4.8.18) introduced a bug that SQL Source Control had some time before: timeouts during checkin! :-( In addition, there are several processes "Red Gate Software - SQL Tools" that all produce massive CPUTime and DiskIO, slowing the whole development environment down. :-( When will a fix be available?

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  18. BUG: Recently edited object disappears from Object Explorer

    Recently edited objects disappear from the object explorer pane after editing an object in designer. For example, changing columns on an existing table which prompts to update a related table will result in the related table being highlighted and the table I was editing disappear from the object explorer pane. The missing object only reappears if I manually refresh the pane. If I don't notice that this has happened, it can be very confusing scrolling through a list of objects trying to finding recent changes. This is a bug.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  19. "SQL user without login" should be supported without Warning

    SQL user without login is not correctly detected by SQL Source Control
    The Warning displayed is confusing

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  20. Source control for replication scripts.

    The ability to maintain replication (scripts) as a source control object.

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
1 2 … 14 16 18 … 29 30
  • Don't see your idea?