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

22 results found

  1. SQL Source Control For Data Updation

    We have gone though SQL source control and it workd perfectly with our Mercurial repository for schema changes. We also want some data changes to be source controlled like in some master tables , we have added some values. We want that these values should be added in the target database with the schema changes when the target db update itself by taking latest, so this type of feature i available in RedGate or we have to do some manual work for data changes. Kindly guide. Thanks

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

  2. Integrate with Fortress Item Tracking

    When checking in changes allow the user to link the changes to a Ticket ID in Fortress Item Tracking, adding a comment to that ticket and adding the ticket ID/details to the checkin comment. Also optionally allow the user to complete the ticket when checking the changes in.

    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…)
    2 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
    completed  ·  Gyorgy Pocsi responded

    Using the latest Vault EA build (1.1.3.49) it’s possible to connect a commit to a ticket id. An example comment you could use to mark bug id 4 as completed:

    Fixing that old bug #4 #completed

    You can use any status string you have in use instead of completed.

2 Next →
  • Don't see your idea?