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

8 results found

  1. When using the 'Push to remote Git repository' feature in SC 4.1.8.41, add functional support for remote Git repositories that use SSH keys for authentication.

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

    SQL Source Control 7 has now been released. In this version, SQL Source Control now uses the Git command line for all its Git interactions, which means it will support any Git authentication method that the command line supports. This includes SSH support. You’ll need to make sure you have your SSH key correctly configured for the Git command line to use.

    You will need to ensure that you have Git.exe available in your system path – the easiest way to do this if you don’t already have Git installed is to download Git for windows (https://git-scm.com/download/win)

  2. When other instances of SSMS are closed, Source Control should be re-enabled.

    1 vote
    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)
    completed  ·  fiona.gazeley responded

    In the Global Options you can choose to allow SQL Source Control to be open in multiple Management Studio windows

  3. Sequence object not yet recognized by SQL Source Control.

    14 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  ·  Better Support for Shared Db Dev Model  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. When I try to commit changes it says unknown user. I believe it is very important to be able to track who's making what changes.

    112 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. When we look at the RedGateDatabaseInfo.xml file, it appears as one long line of text. Merging this is nigh on impossible because the one line conflicts. It would be nice if it was written in a pretty xml format to help with merging

    3 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  ·  Better Support for Shared Db Dev Model  ·  Flag idea as inappropriate…  ·  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. 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. It would be nice if only my changes were shown. There should be someway to filter the list to just my changes, or at least show the username in a column so that it can be sorted on.

    9 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. In a dedicated db model, a conflict will occur when User1 and User2 both make a change to Table1. User1 commits the change successfully. When User2 tries to commit, they will be notified of the conflict. User2 must then decide if they want to take what's in source control or keep their version and commit this to source control. In either case, User2 may need to reapply some changes to the db and re-commit.

    In a centralized db model, when all developers are working against the same db, these conflicts should NOT occur.

    10 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. I recentrly had a brief email exchange with Stephanie from Red Gate, where I explained that we use a centralized Development database, instead of every developer having a dedicated local version of the DB against which they develop. I believe that the Centralized Dev DB model is the model used most in the field, mainly for two reasons. 1) Most companies don't want their developers to have local copies of the database for security reasons, and 2) Development DBs often hold a lot of test data which would not be practical for all of the developers to have locally.

    Having…

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

    SQL Source Control supports either model, http://www.red-gate.com/MessageBoard/viewtopic.php?t=12947.

    v2.0 has the following enhancements for the shared model:
    If you setup your database as shared, then you will see who last updated each object on the Commit tab and Undo dialog. Only objects that you last updated will be checked by default. This will prevent you from accidentally committing/undoing others changes that work on the same db.

    We are also addressing the problem so that you will no longer see invalid conflicts on the Commit tab.

  • Don't see your idea?