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. Why check and re-check for changes so many times?

    Using SSC 3.0.11.3531
    Dedicated development model

    1. We finally get a nice little notification that Commit Tab has been updated. (Kudos for finally doing something in the background and letting users know they have to take action on something)
    2. Click on the notification to open the Commit Tab
    3. Wait for SSC to determine latest version and work out whats changed.
    4. Select my items and say commit
    5. Wait for SSC to once again determine the latest version and work out whats changed and commit my selected changes to TFS.

    Surely
    a) You already know what items are changed in order to show…

    8 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  ·  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. 1) Source Control - Get latest: first schema's then udf's and xsd schema THEN the rest

    1) Source Control - Get latest: first schema's then udf's and xsd schema THEN the rest

    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

  3. Add support for ADD SIGNATURE / DROP SIGNATURE

    Maybe it is a bug. But code like

    DROP SIGNATURE FROM dbo.mySP
    BY CERTIFICATE [myCertficate];

    is not recognized as a change. Please consider to support this

    16 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…)
    1 comment  ·  History/Log  ·  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

  4. RCS Codes interfere with change detection using Perforce

    RCS keyword expansion expansion in Perforce is detected as a change when comparing DB and Source Control code. This is unhelpful. SQL Source Control should ignore changes in RCS tags content when the file type is set to KText

    7 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…)
    1 comment  ·  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

  5. Default constraint names with escape characters aren't registered as a change

    I accidently did an sprename 'DFVisitsSome3234234', '[DFVisits_SomeNumber]', 'Object' and committed it to SVN. Now, when I change it back, the Source Control does not detect this as a change to commit back. How do I get around this, or it's a bug.

    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…)
    1 comment  ·  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

  6. When doing a "get latest", only require read permissions.

    I would like to be able to allow people to get a copy of the latest set of development functions, etc. kept in a repository. I don't want everyone to be able to write new/modify existing functions. Currently when they try to do a get latest, it errors out saying they need read, check in, check out, and lock permissions. To get around this I've given everyone full permissions in TFS. I don't understand why that would be necessary for a get latest.

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

  7. StarTeam

    Include StarTeam as a source control option

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

  8. Needs to be faster when retrieving changes. It takes forever to bring back the list of changed objects after you make a commit. I

    Needs to be faster when retrieving changes. It takes forever to bring back the list of changed objects after you make a commit. I have to make multiple commits at a time, some are single items some are multiple items. Each commit is based on a change set developed in TFS. It takes all day to get through 88 items just because of the time it takes to refresh the list.
    Use a rolling refresh of the list after the initial load, new objects can be added in the background, those that are committed just get dropped from the list…

    27 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…)
    3 comments  ·  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

  9. migration script need names, dates and tagging

    I would like to see more meta data columns on the migration script window. Name and Date create come to mind. Also tagging for specific environments (QA, Prep, etc)

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

  10. Need functionality to view user and database objects dependency

    SQL has the feture to view object dependencies. but, it dont have it for SQL logins. So, it will be good to have this feature in this s/w

    2 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

  11. Cancel commit clears comments

    If I cancel a commit, on the dependencies dialogue window, it seems to clear the original comments.

    This usually happens if I forget to include an object for commit, and the popup dialogue reminds me. I know it offers to include dependencies I have missed, but this often I'll have meant to include other objects in the submit. If I click cancel to go back and add them, the comments have been cleared

    2 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  ·  History/Log  ·  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

  12. BUG: Table stays marked as "changed" even after commit

    The source control system keeps thinking a certain table wasn't committed, and marks it up as "changed" to be committed. Here's the table:

    -- Columns

    CREATE TABLE [dbo].[EvaluacionesCiclosEducativosGruposAcademicos]
    (
    [CicloEducativoId] [int] NOT NULL,
    [EvaluacionId] [int] NOT NULL,
    [Grupo] [int] NOT NULL,
    [ProfesorId] [int] NOT NULL,
    [CursoId] [int] NOT NULL
    ) ON [PRIMARY]
    GO

    It doesn't seem to detect this line, and decides it has to insert it again:

    DISABLE TRIGGER [dbo].[tD_EvaluacionesCicloEducativosGruposAcademicos] ON [dbo].[EvaluacionesCiclosEducativosGruposAcademicos]
    GO

    At the time of this writing, it has inserted the very same section 4 times, one after the other, and wants to keep doing it.

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

  13. Only certain users database should be able to do source control

    I had three different connection in SSMS. One for each user: Sql admin, webadmin, webapplication user. I think I by mistake made a commit from the connection for the webapplication user which have very few rights. All the users right got screwed up after that.

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

  14. Migration script missing extended properties of child tables FKs when making change to parent table.

    Bug: when creating a migration script for a table change that requires dropping Foreign Keys on other tables to this table, the generated migration script does not include the extended properties for the Foreign Keys on the other tables when rebuilding the Foreign Keys.

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

  15. BUG: Expended properties (MS_Description) on tables and DB is ignored

    When I add Extended properties (MS_Description) on tables and Database and tries to commit, the changes dosn't Show.
    If I later change a Description on one of the fields in the table, the Table properties changes is shown (and commited).
    I Cant find a workaround for the DB description

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

  16. Offline Mode

    I develop locally on a laptop. If I want to develop remotely and forget to turn on VPN before I open SSMS and select a database, SQL Source Control has a fit because it can't find the repository. In fact, it becomes unusable until I've connected to the repository and unlink and relink the database in source control.

    An offline mode would detect if the repository was unavailable and merely track changes until the repository is available again.

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

  17. Single click to get latest for all connected databases

    We have a fairly long list of source controlled databases whose changes may affect a developer's local environment. Right now they have to click each database and get latest. It'd be great if they could right-click at the server level and choose "Get Latest Changes From Source Control ..." at that level. It would then pull all the changes for all the databases. I suppose the Get Latest window would have to have a database column.

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

  18. SQL Source Control - Subversion - Switching

    We branch our database often for requirements and version releases. Each version gets a tag which makes it easy to link to the proper version. When bugs come in we need to validate them. One of the steps that needs to happen is we need to make sure our database is on the same version that the bug came in for. The easiest way to do this would be to perform a subversion switch command to the tag in our repository for that version of database. It is very difficult to do this with SQL Source Control as it stands…

    8 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…)
    4 comments  ·  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

  19. Script linked server names

    Imagine we have a complex database which uses a lot of other databases via linked servers. Now imagine it's a dev environment, we put this complex database into SVC and do development.
    The problem begins when we're about to release to a prod environment via RedGate Compare, prod environment has all required linked servers and foreign database with they all come with different names. The inability to use variables inside RedGate makes it difficult to script linked servers and foreign database names. Ideally it could be something like VS Database for Professionals + SQLCMD

    4 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…)
    3 comments  ·  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

  20. Database properties included into stored proc script

    Currently RedGate includes these lines to every stored procedure it puts into SVC:
    "SET QUOTEDIDENTIFIER ON" and the "SET ANSINULLS ON"
    Actually I don't think it makes much sense because these are simply db properties and should be tracked and version controlled as a separate database properties script, but not included into every stored procedure file.
    OR it would be nice if we simply can turn it off.

    4 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  ·  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
1 2 … 17 19 21 … 29 30
  • Don't see your idea?