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. Allow SQL source control to cascade deletes when the database does not have cascading deletes enabled.

    When we hop back in our source control repository to an older release and "update" our database, occasionally there is new static data that is referenced by non-static entries in the database. We do not have cascading deletes enabled for various reasons outside of the developers control, but in this particular instance it causes errors when static data is removed from the database to revert to an older version. Would it be possible to have redgate check incoming foreign keys and generate all the necessary deletes to allow static data removal?

    3 votes
    0 comments  ·  Static Data  ·  Admin →
    How important is this to you?

  2. Partitiong Functions

    Without any changes on the database, SQL Source Control creates a tracked changed alternating between these two partitioning functions:

    CREATE PARTITION FUNCTION [TranDate] ([datetime2] (0))
    AS RANGE LEFT
    FOR VALUES (N'2007-01-01 00:00:00', N'2008-01-01 00:00:00', N'2009-01-01 00:00:00', N'2010-01-01 00:00:00', N'2011-01-01 00:00:00', N'2012-01-01 00:00:00', N'2013-01-01 00:00:00', N'2014-01-01 00:00:00', N'2015-01-01 00:00:00')

    and

    CREATE PARTITION FUNCTION [TranDate] ([datetime2])
    AS RANGE LEFT
    FOR VALUES (N'2007-01-01 00:00:00', N'2008-01-01 00:00:00', N'2009-01-01 00:00:00', N'2010-01-01 00:00:00', N'2011-01-01 00:00:00', N'2012-01-01 00:00:00', N'2013-01-01 00:00:00', N'2014-01-01 00:00:00', N'2015-01-01 00:00:00')

    Could something be done about it?

    5 votes
    1 comment  ·  Better Support for Shared Db Dev Model  ·  Admin →
    How important is this to you?

  3. spinning wheel icon

    After creating the database, I added to the shared database model and commited the objects to the repository, but the spinning wheel is not gone and it looks like it is busy or just unable to reset the icon. Even after I disconnect from the database server in my SSMS, my cursor still has the spinning wheel on it. Looks like a bug and it is really annoying and confuses the hell out of users about the status of Source Control process.

    5 votes
    0 comments  ·  Better Support for Shared Db Dev Model  ·  Admin →
    How important is this to you?

  4. Red Gate Source control should only need one workspace

    Red Gate Source control should only need one workspace. Is there a specific reason Red Gate creates multiple workspaces per database linked? This is creating a mess of my workspaces.

    58 votes
    5 comments  ·  Initial Setup  ·  Admin →
    How important is this to you?

  5. Login information for SQL Source Control

    Where login information is stored for SQl Source Control 3? If A user is using B users SVN credentials and later on A user get its own SVN credentials. How user A can force SVN to ask his own credentials?

    4 votes
    1 comment  ·  Better Support for Shared Db Dev Model  ·  Admin →
    How important is this to you?

  6. Migration Scipts picking up non-selected commits

    When creating the migration script if the developer goes through "cherry-picking" the commit(s) that they wish to include in the migration script. It appears that non-selected commits that are between the selected ones are being picked up.
    For example if the developer chooses commit 1 and 3 and skips 2 the objects in commit 2 are still showing in the migration script.

    I would like to point out that this appears to be a bug and not a feature request, but i am still using 3 votes...

    3 votes
    1 comment  ·  Admin →
    How important is this to you?

  7. updated data on static tables

    Disable Foreig Keys of table of transaction

    1 vote
    1 comment  ·  Static Data  ·  Admin →
    How important is this to you?

  8. Installer to offer option to remove older version log folders

    Suggest that the SSCv3 installer NUKE all prior version Log folders e.g., SSCv2 and SSCv1, please...(or at least offer us the choice to have them nuked...) Had Stuart not posted (at http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/2526239-log-files), I'd have those two folders around for ever...

    2 votes
    0 comments  ·  History/Log  ·  Admin →
    How important is this to you?

  9. DataLink

    Just view the tables checked as static.
    Comes in handy when comparing to other Databases (hence same database but for instance on another level -> DEV-TST-ACC-PRD)

    1 vote
    0 comments  ·  Static Data  ·  Admin →
    How important is this to you?

  10. Do not check all the items to be committed by default

    After the list of change to be committed get refreshed, every item get checked by default, even those I just unchecked. Is it possible to not check the item if it was already in in the list and unchecked, or just mark them all as uncheck by default instead of being checked.

    The issue is when I have item that I don't want to commit right now (unstable, unfinished view, etc), I have to uncheck them EVERY time the list is refreshed, which is, every often since the list refresh each time you click on a new object in SSMS.…

    13 votes
    0 comments  ·  Admin →
    How important is this to you?

  11. Commit data and schema changes separetly

    A table is under source control and the data of that table is linked as static data.
    Both table definition and data has been changed and are visible in the 'Commit changes' tab.
    Since the data is just edited and changed for development purpose it should not be committed.
    But in this situation it is impossible to only commit de table definition.
    When checking the table the data is also checked (and the other way around also).

    It would be nice to be able to commit the changes separetly.

    20 votes
    1 comment  ·  Static Data  ·  Admin →
    How important is this to you?

  12. Migration Script Rollbacks

    The only obstacle I have with switching to SQL Source Control 3 as a complete solution to source controlling and deploying is its inability to rollback custom code in a Migration Script. I would like when creating a Migration Script the ability to create a Reverse Migration Script so that if I use SQL compare to roll a code push back to a previous version in source control, it will grab the reverse script the same way as it grabs the migration script currently when pushing.

    For example, if my migration script has an update statement in it to modify…

    94 votes
    4 comments  ·  Admin →
    How important is this to you?

  13. Better support for transactions and error handling in migration scripts

    The migration scripts that are generated don't fit in well to the other code that SQL Compare generates to update a database. In general, the SQL Compare script will have the script that SQL Compare generated, followed by the migration script, and then more SQL Compare generated script. SQL Compare will wrap its sections with BEGIN TRAN and COMMIT TRAN, and have lots of error handling, but the migration script has no error handling and is not part of the larger transactions. This can cause problems where the scripts succeed partially and it can be hard to recover from that.

    …

    16 votes
    2 comments  ·  Admin →
    How important is this to you?

  14. SQL Source Control support SQL Server maintenance jobs

    It would be mint* to be able to have SQL Server Maintenance jobs included in SQL Source Control. Could it be added as a new feature?

    • (see kid from Super8 movie)
    29 votes
    1 comment  ·  Better Support for Shared Db Dev Model  ·  Admin →
    How important is this to you?

  15. GUI bug: white square on setup page

    1 vote
    1 comment  ·  Initial Setup  ·  Admin →
    How important is this to you?

  16. Analysis Server (SSAS)

    Support for Analysis Services Databases

    21 votes
    1 comment  ·  Admin →
    How important is this to you?

  17. Connections to TempDB

    With a team of 6 using source control, we are finding the performance of both SSMS on individual machines and our developement SQL box to be crippled by Source control.

    Our developement server is showing literally hundreds of connections to TempDB from Sql source Control which is slowing the box considerably

    4 votes
    2 comments  ·  Admin →
    How important is this to you?

  18. On screen alterts

    On the commit tab, if I select any row where changed by is not me a warning appears at the top "Some of the changes may not have been made by you"

    This has the effect of pushing everything down the screen and what was under the mouse is now moved.

    This is extremely annoying, it would be better to have the warning appear in a dedicated area of the screen that doesn't cause it to change.

    0 votes
    0 comments  ·  Admin →
    How important is this to you?

  19. Automated Deployment based on TFS work item status

    I would like a way for SQL Source control to leverage TFS work item status and facilitate automated deployment similar to lab management.

    13 votes
    0 comments  ·  Support Additional Source Control Systems  ·  Admin →
    How important is this to you?

  20. Partition scheme Bug?

    We have a partition scheme setup using a function

    CREATE PARTITION SCHEME [partitionSchemeSystemId]
    AS PARTITION [partitionFunctionSystemId]
    TO ([PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY], [PRIMARY])

    when SourceControl has populated SVN it has added an extra partition to the scheme

    Sourcecontrol sees these as being the same between the DB used to populate SVN but when we link a new instance of the database to sourcecontrol it identifies a conflict

    4 votes
    0 comments  ·  Initial Setup  ·  Admin →
    How important is this to you?
1 2 … 18 20 22 … 29 30
  • Don't see your idea?