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. I am trying to pick my tables for the static data feature I just dound and i'm using "explore data" to find the table I want to store the data for. The popup however is modal so I cant scroll the data explorer without saving the ones I just ticked.

    11 votes
    0 comments  ·  Static Data  ·  Admin →
    How important is this to you?
  2. 15 votes
    2 comments  ·  History/Log  ·  Admin →
    How important is this to you?
  3. 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 IDENTITYINSERT 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 IDENTITYINSERT diffs and merges would be easier.

    530 votes
    How important is this to you?
    under review  ·  Kendra responded

    Thanks for this suggestion and for the many comments and upvotes. I realize that this is a pain point.

    I have a few shorter-term workarounds to summarize as well as some information on the longer roadmap in this update. I know these shorter-term workarounds aren’t perfect (I summarize the pros and cons), but I’m posting them as they may help a few folks.

    Workaround 1) When data changes to static data need to be made, use a “relink the table” pattern
    One can “cleanly rescript” a static data table in SQL Source Control by:

    • Unlinking the static data table
    • Committing
    • Relinking the static data table
    • Committing

    Pro: This works with the GUI and requires no special knowledge or comfort with TSQL. This may help folks with just a few static data tables.
    Con: This requires extra steps and results in extra commits in the history, which I realize can…

  4. We branch our database often for requirements and version releases. Each version gets a tag which makes it easy to link to the proper version. When bugs come in we need to validate them. One of the steps that needs to happen is we need to make sure our database is on the same version that the bug came in for. The easiest way to do this would be to perform a subversion switch command to the tag in our repository for that version of database. It is very difficult to do this with SQL Source Control as it stands…

    8 votes
    How important is this to you?
  5. Multiline replace would be a nice feature. Like standard SSMS "quick replace" (ctrl+h), but with ability to add line breaks to both "find what" and "replace with".

    1 vote
    0 comments  ·  Admin →
    How important is this to you?
  6. We use a shared environment, and if someone forgets to check something in, then the changes made appear as if from the next user to edit the item.

    4 votes
    How important is this to you?
  7. Imagine we have a complex database which uses a lot of other databases via linked servers. Now imagine it's a dev environment, we put this complex database into SVC and do development.
    The problem begins when we're about to release to a prod environment via RedGate Compare, prod environment has all required linked servers and foreign database with they all come with different names. The inability to use variables inside RedGate makes it difficult to script linked servers and foreign database names. Ideally it could be something like VS Database for Professionals + SQLCMD

    4 votes
    How important is this to you?
  8. Support multiple SYNONYM definitions depending on which server (dev, test, prod) the source is being extracted to.

    25 votes
    How important is this to you?
  9. Could you please add a feature that would allow one to view the 'dependencies' when on the 'Commit to source control' window appears.

    This would be useful to see which of the tables you are about to commit relates to the 'dependencies' tables in the pop up.

    2 votes
    How important is this to you?
  10. Better support for the "Use case-sensitive object definition". Especially for changes in columns that are used in foreign keys. Now it is possible to commit changes such that the "Use case-sensitive object definition" cannot be used anymore.

    1. Link the database to source control with “Use case-sensitive object definition” turned off (which seems to be default?)
    2. Create two tables, one with a foreign key referencing the other table.
    3. Save these tables to the working folder
    4. Alter the case of the field referenced by the foreign key and alter something else on the same table too. That way the change in case…
    4 votes
    How important is this to you?
  11. To enable deterministic testing using tSQLt, we replace any system calls to non-determinstic native functions like GETDATE() or GETUTCDATE() with [dbo].[getdate] user defined scalar functions (which we can then which to [test].[getdate] as part of tSQLt testing). Unfortunately it seems RG Source Control trips up on this and fails to recognise these as valid functions in the [Get Latest] tab. This means that we can't deploy using RedGate Source Control as it's usage is pretty ubiquious and with this being ignored many of our other functions fail to deploy.

    3 votes
    1 comment  ·  Admin →
    How important is this to you?
  12. No Category for BUGS? When comparing the TFS version to live DB in SSMS, objects missing from live DB don't cause the "change" visual queue. One must select the DB/SQLSource Control/Get Latest Tab to realize there are extra items in the DB. SQL compare does not have this issue.

    3 votes
    How important is this to you?
  13. It would be nice to allow comparison "solutions" where you could have multiple projects bundled together. The solution comparison could be run in a single step, and all projects would be run with results in separate tabbed windows. For example, on a weekly basis I need to compare DEV and LIVE schemas for nine databases. I have nine separate projects that I need to open and run. If I could bundle these into a solution, run the solution and have all nine projects run and get their results displayed in tabs, that would save a ton of time.

    8 votes
    How important is this to you?
  14. 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
    5 comments  ·  Static Data  ·  Admin →
    How important is this to you?
  15. We often restore databases into our working folder and would love an option to simply bring that database up to the latest source controlled version. Right now when we restore a database Source Control thinks we made a bunch of changes so we end up having to "undo" those changes.

    29 votes
    How important is this to you?
  16. On the "Commit Changes" and "Get Lastest" tab, you should include the last date the object has been modified. So you will be able to sort/filter the objects recently modified.

    46 votes
    2 comments  ·  History/Log  ·  Admin →
    How important is this to you?
  17. Most objects are shared among our several databases, while some only apply to some (or only one) of our databases. Add the ability to ignore objects by database by right-clicking the database object and clicking a menu item like "Ignore this object in this database" and/or "Ignore this object in all databases except this database". So then we don't need to have an object in one/many of of our databases that is not used in that database(s), source control would not show the need to be updated or added because it is on the ignore list for that database.

    4 votes
    How important is this to you?
  18. When adding a static data table to source control, there should be a warning if that table has a foreign key constraint on another table and give the option to include that table as static data also. As it is the error you get in SQLCI is quite hard to decipher when SQL Source Control is used in conjuction with SQLCI.

    3 votes
    0 comments  ·  Static Data  ·  Admin →
    How important is this to you?
  19. We use SQL source control linked to Gerrit. It would be really useful to be able to 'Amend last Commit' inside the GUI.

    4 votes
    How important is this to you?
  20. When you hit get latest and your stored procedure contains an error, it fails to get the latest. It doesn't give a clue in which piece of code the error is located

    1 vote
    1 comment  ·  Admin →
    How important is this to you?
1 2 9 11 13 29 30
  • Don't see your idea?