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

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

588 results found

  1. When comitting:
    Andy makes an edit and "Changed By" shows "Andy" (but does not yet commit).
    James then makes an edit and "Changed By" is now "James", but does not mention "Andy"

    It would be useful if it could show "Andy, James", to highlight a potential conflict.

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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)
    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)
  3. 2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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)
    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)
  5. 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)
    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)
  6. 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)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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)
    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)
  8. If a table is linked as static data, any changes to the data should automatically be included in the migration script, just as changes to the schema are. Having to write a manual script or use the separate compare tool is extra work, and small changes are easy to miss.

    43 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Static Data  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. I have a table type with "(IGNOREDUPKEY=ON)" on it. Sql Source control doesn't preserve this and doesn't see this in the SqlServer database schema on the table type

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. If I make a change to a proc in management studio editor, then execute the alter. That change is not reflected in object explorer until i do a refresh of object explorer. After the commit SQL source control still show a change and this can result in your change reverting if you press commit again. Therefore sql source control should do a refresh of the committed object in object explorer after every commit.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. When adding a static table to be managed by SSC the comparison key is automatically selected. Our tables have auto generated INT ID columns as PK used in FK's. In our Static Data tables we have other columns that are unique and for them we have UK’s that we would like to use as the comparison key.

    Here is another with the same issue...
    http://www.red-gate.com/messageboard/viewtopic.php?t=16498&highlight=comparison+key

    I have not found any workaround for this yet at least.
    I believe that this would be a great improvement for SSC and would be used by many. If you agree please vote for this…

    83 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Static Data  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. It would be more than a 'nice-to-have' if we could specifically select and label versions as a "Release". The current assumption is that selecting a specific revision is equivalent, but there are scenarios where it is necessary to keep release a build that spans "revisions" - especially when working on an incremental set of changes.
    The only way I can see to do this right now is to restore all relevant versions individually and then use SQL Compare to manually revert those changes that have been committed in the "current" build but which wee do not want to release yet…

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. The "toast" / desktop alert popups by the system tray always seem to show on my primary monitor (where my start menu is). However I often have the app running on my secondary monitor and it would make more sense if the popups displayed on the same monitor as the window where the action triggered the popup

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  16. Ignore names generated by SQL Server (such as Primary Keys, Defaults etc)

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  17. A while ago I had discussed with Redgate about how to allow sql source control to create scripts for releases to deploy db changes.
    This mostly works, except when there are changes that require more logic to properly handle existing data when certain db object changes are made.

    For instance, adding a new column to a table (that has data in it) that is required, but does not have a default.

    The current way of handling this is to create a custom script for that change at the time of check in. The problem with this is that it requires…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  18. 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)
    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)
  19. Normally, I can use RedGate's analysis of what SHOULD be retrievable from source control, or what SHOULD be commitable.

    Under certain circumstances, however, I know better than the tool does. For example, I might want to roll back a set of routines and/or tables to what is in revision control.

    Currently, I have to "jump through hoops" to do this. I have to do multiple steps, some of them crazy ones such as using "undo" counterintuitively (for instance, undoing a "drop" to actually get something that is missing).

    ** Can you give us a screen or a button or selector…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  20. 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)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?