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

2 results found

  1. Bug (shared model): Tables with extended properties still highlighted after commit.

    SSC 3.1.0.4829
    SQL Server 10.50.4000
    Shared model

    After adding an extended property to a table the recognition and the commit work fine. But after having committed the changes the table will be remarked as having pending changes in the object explorer of SSMS. In the commit changes tab there are no changes to commit which is correct.

    Maybe also extended properties with other objects are affected.

    14 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
    declined  ·  Michelle Taylor responded

    This looks like something we’d prefer to handle as a bug report than a feature request – if you are still experiencing this problem, please email support@red-gate.com with the details.

  2. Add support to SQL Source Control for generating upgrade scripts to a SQL Azure database

    If you have only the SQL Source control product, you can use it to upgrade your production SQL server database. But if you switch to Azure SQL, you lose this capability. I think the option to generate upgrade scripts that are Azure compatible would be great!

    20 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
    declined  ·  AdminStephanie (Product Manager, Redgate) responded

    We do not recommend connecting a production database to SQL Source Control. We recommend using SQL Compare for deployment and you can deploy to Azure databases with SQL Compare.

  • Don't see your idea?