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

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Better Support for Shared Db Dev Model  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Better Support for Shared Db Dev Model  ·  Flag idea as inappropriate…  ·  Admin →
  4. Drop statement in script

    Would be nice to have the option to include the drop statement inside of each object script. The option would be global over all scripts.

    `EX: IF (OBJECT_ID('MyTable') IS NOT NULL) DROP TABLE MyTable`

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Better Support for Shared Db Dev Model  ·  Flag idea as inappropriate…  ·  Admin →
  5. Shared Model - multiple instances of the same DB

    Most of our enterprise applications have mutiple instances of the same DB schema. We use the shared model and would like to update al instances once we commit changes on one of them. As a workaround we commit the changes and then hit revert changes on the instances we need to update

    70 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Better Support for Shared Db Dev Model  ·  Flag idea as inappropriate…  ·  Admin →
  6. Commit dependencies dialogue blue dot.

    Commit dependencies dialogue shows blue dot on objects even when those objects have no changes to commit. This seems incorrect.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Better Support for Shared Db Dev Model  ·  Flag idea as inappropriate…  ·  Admin →
  7. Make it clearer when there is a new Filter available

    If there is a new Filter available at the moment this gets listed in the Get Latest tab with all other objects. Really you should apply this first before committing changes or getting latest. If you don’t there’s a danger you commit or get objects that should be excluded by the filter.
    For example if a new filter excludes Users and Roles, but you fail to synch this before committing latest you can easily commit recently created users and roles that should simply have been excluded.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Better Support for Shared Db Dev Model  ·  Flag idea as inappropriate…  ·  Admin →
  9. Relocate

    Be able to apply the SVN Relocate command. I often switch between our SVN server while on the LAN, but then when on the road I connect "relocate" to the SVN server using external IP address of the server using the SVN relocate command.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. Connect same database to multiple branches

    We use the shared database development model and can have several projects going at once. Some developers may jump back and forth between projects. It would be nice to have the ability to setup a single database connection to multiple branches. Possibly using the SSMS registered server name instead of the physical server name.

    33 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. Prevent user from committing other user's changes

    One of the problems with a shared db model, where all developers work against the same database, is that everyone's changes are listed on the Commit List and any user can commit any other user's changes. It would be nice if an administrator setting could be set that would only allow users to commit their own changes There should be someway to prevent other users from committing your changes.

    76 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. Allow "Get Latest" in shared model

    We occasionally restore a copy of production db over our development db. With SCC in place I imagine it will work like this:

    1) Everyone commits dev changes that they care to keep

    2) perform restore

    3) One person relinks SSC in dedicated mode and uses "get latest" to pull down latest schema to the newly restored dev db.

    4) everyone can resume working in shared model.

    To cut out the relink in step 3, it would be nice to be able to use the "Get Latest" tab in shared model for occasions like this

    34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. Fortress - Exclusive Checkout / Object - Lock

    Similar to how fortress works with visual studio. All objects in the database would require an exclusive or shared lock to be worked. If an object is changed without a lock it becomes renegade for that user.

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
1 3 Next →
  • Don't see your idea?

Feedback and Knowledge Base