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. 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)
    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. Back in Visual Source Safe Days, we had the ability to add a macro to the comment block of our procedures and functions. It was something like $HISTORY$.

    When checking in our code, it would add whatever comments we added to the procedure automatically.

    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)
  3. We're using Dynamsoft SCM for source control. Currently, we're using sql prompt/sql changeset to script to a folder and then push that into SCM. It supports the SCC interface, but since you guys said that was too unreliable to use we're pretty much stuck.

    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)
  4. Is it possible to tell the tool to release memory. I notice it consumes an enormous amount which I can understand, but would like to release it once I'm finished using the tool. I understand it will have to consume the memory again next time it compares my db to the repository.

    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)
  5. I word like to hav the posibility to revert changes using a rightclick i history.
    Both all (opper pane) the changes in a commit, and the changes to a specific object (middle pane).

    7 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  ·  History/Log  ·  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. 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)
  7. Currently I find the filter rules implementation a bit clunky. I personally would prefer to be able to source control individual database objects explicitly. For example, it would be nice to be able to right-click on a database object in SSMS and have the option to add it to source control. This could have the effect of adding an "Include if object name equals xxx" filter rule.

    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)
  8. Whe you have a multi branched dababase environment could be helpful to export from the main database the list of tables linked (in xml ie, or json, as you wish), in order to reload it on the branch database. Obviously only for the objects that exist. An alternative could be to save to "other similar database" too..

    7 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. RCS keyword expansion expansion in Perforce is detected as a change when comparing DB and Source Control code. This is unhelpful. SQL Source Control should ignore changes in RCS tags content when the file type is set to KText

    7 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)
  10. It would be nice to do a quick search across all migration scripts for certain keywords. I.E. I'd like to look for all migration where I granted permissions. Or where I inserted rows into a specific table.

    7 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  ·  History/Log  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. I see the changes to be checked in , these may have been done by other developers. I want to compare the changes about to be checked in against the previous version to see what changed before I check in.

    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)
  12. Need to have better support for contained databases feature of SQL Server 2012. For example a new feature - user WITH PASSWORD is scripted as a user WITHOUT LOGIN.

    7 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)
  13. When developing in shared enviroment, I'd love a history tab that I can review all revisions with details, and not have to have a modal window separately. I believe this should be integrated into the main source control tab as change history log. This could help make others aware of changes made that could affect them, yet were already committed. Thanks!

    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 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)
  15. Auto create migration scripts prior to a comit.
    I would like to sugest that SQL Source control should have the ability to auto create migration scripts prior to a comit. This should be a configuarble option that can be enforced at the database level. By offering this we as developers could see and archive the expected migration path from x to y to z. Obviously any auto created migration script should still be editable as it is now.

    Thanks

    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)
  16. In our System we have 2-3 predefined Roles that the application uses to run against.

    The Issue I am running into is when scripting the roles i don't want all the sp_addrolemember being scripted into source control as the users using the role will be different in different environments. So it will always show up as a diff if the Role is already created and assigned to a user.

    I would like suggest adding those sp_addroletomember scripts be configurable to be scripted in the User object they belong to instead of in the Role Object

    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)
  17. It's far too difficult to find the Filter and Comparison Options items if there are lots of things that might be filtered out or excluded via options. These items should always show on top regardless of the UI sort order because they are so important to synchronize first.

    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)
  18. If a table is setup for static data, and you remove one or more columns from that table, the static data is not updated in the working directory when "Saving changes".

    7 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)
  19. If you have a HiDPI or 4K display, SSMS is scaled to 2x. In SQL Source Control, The Commit and Get Latest tabs are fine, but the Migrations, Locking and Setup UI are scaled MUCH larger than 2x. I would prefer those UIs be scaled to 2x.

    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)
  20. 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…

    7 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)
  • Don't see your idea?