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

177 results found

  1. 49 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)
  2. 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)
  3. For continuous integration purposes, I would like to commit schema changes with changes in my project (e.g. C#) so that any related changes to classes / unit tests are commited in the same revision.

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

    In SQL Source Control v3.4, there is now an option to link your database to a working folder. On the commit tab, there is an option to “Save” the database changes to the working folder. This scripts the objects and static data to files. You can then use your own version control system’s tool to commit the changes alongside other changes that also exist in this area. The folder for the database needs to be separate from the other files, so it might be nice to have a top level project folder with a folder for the application and another folder for the database below. Therefore, to commit both application and database changes, you would commit from the higher project folder. You can also have more folders for documentation and other things that you want to source control.
    http://www.red-gate.com/products/sql-development/sql-source-control/

  4. 17 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  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)
  5. Currently there are only choise of SVN and TFS but I think that support of the Mercurial would be really convenient.

    86 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)
  6. It would be really nice if there was a way to checkout or lock db objects so that I know that I'm the only person working on this object and I will not experience any conflicts when I go to commit the object.

    242 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    35 comments  ·  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)
    completed  ·  Gareth Bragg responded

    With SQL Source Control 4.0, we have introduced our new Object Locking feature!

    This feature allows users to lock the SQL object directly on their database server, meaning other users on the same server cannot make changes until you finish you work and release the lock.

  7. If i make a table column which was nullable initially to a non-nullable; and then commit this change to svn. On the other computer, when i update from svn, what happens to the data? as the records in this table may have the null values in the column i just changed.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  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)
  8. Can we have control over how often the source control / database is polled for changes? I see the changes are reflected almost immediately but reallly i dont need it to run that often - Can you let me configure how often the change polling occurs.

    30 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  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)
  9. Keep Mine has always worked fine for me until today. Now when I click on keep mine it doesn't let me mark the SP as resolvable but if I choose take theirs it does.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  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)

    If you want to “Keep Mine,” then you need to be on the Commit tab to see the checkbox at the top get selected. Nothing happens until you actually hit the Commit button.

    If you want to “Take Theirs,” then you should be on the Get Latest tab. Again, the radio buttons at the bottom just acknowledge what you want to do with the object, but nothing happens until you actually click the “Get Latest” button.

    So, if you’re on the Get Latest tab, you can say Keep Mine, but you won’t be able to do anything with that object until you go to the Commit tab. If you are in the same SSMS and you switch tabs, then we should remember your “Keep Mine” acknowledgement and this object should be selected on the Commit tab.

    I hope this helps.

  10. When I first pull up the interface when I'm about to commit some changes (whether via the context menu in the Object Explorer or just clicking into the SQL SC window), you list all changes and select them all by default. That's not a big deal. The problem is, if I try to uncheck one item (not the check box at the top of the list) you'll uncheck ALL items since they're ALL highlighted.

    This isn't normal UI behavior. If I'm checking one checkbox, I mean to check that one checkbox, not everything selected, even if I have them all…

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  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)
    completed  ·  Elizabeth Ayer responded

    Hello! We fixed the issue with weird checkbox behaviour quite a long time ago. If you’re still now happy with how selection works, could you please let us know?

  11. You really should take a look at Tortoise. They've been doing this for a while and they really do a great job most of the time.

    When I commit and it succeeds, I need the revision number that the commit generates for logging/tracking purposes. Your interface just skips over that, hiding all the information that SVN is likely returning (Tortoise will even show us what it's doing during the commit). For me, the more important thing is getting that revision. Otherwise, I have to go into a project (non-SQL) and do an update or grab the log...neither of which you…

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  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)
  12. I have a stored procedure sprunfacttoreport. I renamed it to sprunfacttorpt and now it is no longer in version control and changes are not propagated.

    I don't mind if rename is handled by delete and add rather than svn move, but I would like every object I create to be in version control! :)

    0 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  ·  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)
  13. I'm getting the following error when adding the objects to subversion for the first time.
    It breaks in the following partition function:

    CREATE PARTITION FUNCTION FDICPeoRangePartitionFn(smalldatetime)
    AS
    RANGE LEFT FOR VALUES('12-31-1975')

    This is the error:

    Failed to update:

    oEc.#8Jf: Errors occured whilst parsing file C:\Red Gate\SQL Source Control 0\WorkingBases\3no2fm25.di2\Storage\Partition Functions\FDICPeoRangePartitionFn.sql

    'line 3:14: unexpected token: [",",<642>,line=3,col=14] [char=102]'
    ---> #Eyg.#Lyg: Errors occured whilst parsing file C:\Red Gate\SQL Source Control 0\WorkingBases\3no2fm25.di2\Storage\Partition Functions\FDICPeoRangePartitionFn.sql
    'line 3:14: unexpected token: [",",<642>,line=3,col=14] [char=102]'
    ---> line 3:14: unexpected token: [",",<642>,line=3,col=14] [char=102]
    --- End of inner exception stack trace ---
    at #Eyg.#Gyg.#CGh(FileInfo file)
    at…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  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)
  14. I find the "Recent Messages" button on the TortoiseSVN Windows client extremely useful. I really miss this feature on SSC.

    40 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  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)
  15. We need SQL Source Control to comply with the policies in force for the project. eg. Checkin policies, associate with workitem policy.

    57 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  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)

    SQL Source Control 3.3 now evaluates TFS policies when committing DB changes. For more information see http://documentation.red-gate.com/display/SOC3/This+commit+doesn%27t+meet+the+server%27s+policy+requirements%2C+or+the+policy+isn%27t+configured+on+your+machine.

    To upgrade, use SQL Source Control’s “Help > Check for Updates…” menu item, or download directly from http://www.red-gate.com/dynamic/products/sql-development/sql-source-control/download.

  16. Failed to update:

    oEc.#8Jf: An item with the same key has already been added. ---> System.ArgumentException: An item with the same key has already been added. ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 619, offset:110 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 4199, offset:21 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 4198, offset:578 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 4148, offset:1363 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 4148, offset:1098 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 4145, offset:8 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 67, offset:77 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 71, offset:40 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 3984, offset:137 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 3958, offset:472 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 602, offset:614 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1792, offset:37 ---> SmartAssembly.SmartExceptionsCore.UnhandledException:

    6 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  ·  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)
  17. I have just tried to link a pre-existing data database to Source Control and have come across an interesting error. Having written all the information to the source control repository it appears that the application then attempts to retrieve information back to ensure that it has the most up to date information. At this point it throws an error and points the blame at a line in my usp that is referencing a table that is called audit.Load. Is ".Load" causing the error as the software attempts to parse the file?

    (I can send you the actual error text if…

    6 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  ·  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)
  18. 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)
  19. I got an error when there was a stored procedure that the table had an alias as GO and it didn't let me commit any changes or get latest

    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  ·  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)
  20. The WorkingBases are saved on disk C:\Documents and Settings...”.
    To save disk space on C:\, we would like the Working Bases on the disque D:\ (we have databases with more than 5000 procs). Is there a setup somewehere ?

    47 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Initial Setup  ·  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)
  • Don't see your idea?