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. Ungroup Source Control Commenting

    Is it possible for the comments window to hold a comment per object rather than as a group? That way I can quickly individually comment multiple objects and check them all in in one go.

    6 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  ·  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)
    Close
    Close

  2. Include Ad Hoc Scripts in SQL Source Control

    Whether server configuration, replication scripts, SQL agent Jobs, Powershell, or just test scripts, give me a folder in VCS that I can store and retrieve scripts from. Even if this is to/from a specific folder on my machine, make this an easy process to keep development code with my database.

    79 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…)
    7 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

  3. I just installed a "minor update". If it is minor, why are you prompting me to read a 19 page, 7,500 word licence agreement?

    Only display changes to the agreement and stop wasting my time.

    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

  4. Include miscellaneous options / database properties

    SQL Source Control tracks options like Default Collation. It would be useful to extend this to include all options that can be configured e.g. Recursive Triggers.

    6 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  ·  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

  5. Functionality after restore from command

    After we have run a restore database command, the source control do not notice, that some, earlier loaded stored procedures from lastest version are after that newly out of date.
    Source countrol should recognize a restore and scan completely new for the latest changes.

    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  ·  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)
    Close
    Close

  6. With Many databases source controlled. It would be great if there was a function to view changes and updates across all databases

    With Many databases source controlled. It would be great if there was a function to view changes and updates across all databases. At the moment databases have to be updated one by one. very time consuming

    36 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  ·  Support Additional Source Control Systems  ·  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. Multiline replace

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

  8. Sort constraints / indexes by name

    it would be nice to have the constraints sorted by type and name in the table scripts (this one that are checked in to SVN and are used to show me the differences)

    Example: I have a table with 11 FKs which I will see as
    ALTER TABLE [pld].[tvertraege] ADD CONSTRAINT [tblfk4] FOREIGN KEY ...
    ALTER TABLE [pld].[tvertraege] ADD CONSTRAINT [tblfk3] FOREIGN KEY ...
    ALTER TABLE [pld].[tvertraege] ADD CONSTRAINT [tblfk6] FOREIGN KEY ...
    ALTER TABLE [pld].[tvertraege] ADD CONSTRAINT [tblfk7] FOREIGN KEY ...
    ALTER TABLE [pld].[tvertraege] ADD CONSTRAINT [tblfk5] FOREIGN KEY…

    5 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. For 'Commit changes' the button to refresh is on the far right. For 'Get latest' the button is on the far left side of the window.

    Consistency is king. Having the buttons always at the same place makes it easier. So, either you have both refresh buttons on the far right or on the far left side of the window. I personally prefer the left side as this is closer to the tabs. But that's just 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  ·  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. Do not allow to commit changes to an object that is locked

    I don't see why is good this product if it's posible do commit to an object that is locked. If the object is locked this means that the user is editing it Then why allow to commit to this object

    5 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

  11. The ability to filter by change type, object name, type, owner, etc in addition to the default of showing all changed object

    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…)
    2 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

  12. Increase Max character length of lines before word wraps (160 too small)

    5 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  ·  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)
    Close
    Close

  13. Do not recreate tables when changing a computed columns

    It is very annoying that Source Control always recreates a table, just because I change a computed column instead to drop / recreate only the column (the FORCE-COLUMN-ORDER option is set to false so this could not be the reason).

    Particulary if it is on one of your big tables with lots of indexes, FKs ...

    I know there may be reasons to recreate a table if you add / drop / alter columns (because of possible page splits) but I want to decide it by myself (e.g. by adding a migration script for this rare cases)

    10 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

  14. Performance: Use all available cores when "registering database"

    The performance of the get and commit tabs is still very poor. AFTER querying the structure and content from the sql-server, which of course uses all cores to answer the query, only one core is used for the further comparison by SQL source control (shown as "registering database"). This step takes the longest amount of time, so optimizing SOC to use all cores for that operation should speed up the whole thing. Our developers have machines with 8 cores, so this is a huge waste of available ressources and time and thus money.

    71 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. When a user closes a session/SSMS it would be useful to have the user to prompted about any pending check-ins (shared db).

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

  16. Could you please add a feature that would allow one to view the 'dependencies' when on the 'Commit to source control' window appears. It wou

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

  17. Use case-sensitive object definition

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

  18. Fix a bug where some objects in source control are forcefully ignored due to how they're named

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

  19. ignore constraint table default

    Separate edit filter rule to ignore constraint names that define a default value for a column

    6 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

  20. Warn when adding static data tables that have foreign keys

    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
    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  ·  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)
    Close
    Close
1 2 … 7 9 11 … 29 30
  • Don't see your idea?