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. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    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)
  2. I had disconnected a DB from source control due to performance issues. I have a work-around supplied by RG tech support. When I tried to re-link, I got this message and I am unable to link to the DB in source control.

    Failed to update:

    oEc.#8Jf: Failed to locate the target table [dbo].[Transaction] for the FKTransactionDataTransaction foreign key. ---> RedGate.SQLCompare.Engine.SqlCompareException: Failed to locate the target table [dbo].[Transaction] for the FKTransactionDataTransaction foreign key. ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1435, offset:37 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 211, offset:38 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1369, offset:0 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @

    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)
  3. I've created new link to some DB, then commint changes. Then... i've linked some other DB to prevously created link. Now i have many conflicts. For example:
    "create procedure dbo.proc1" a version in DB and "create procedure proc1" a version in source control. In my opinion by linking to existing DB in source control get lates step should be done. To equal both versions.

    1 vote
    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)

    If your database matches what is in source control, we now update your underlying working folder after you link a db so that you don’t see these conflicts on the Commit/Get tabs.

    Thank you!

  4. If someone drop a object and commit it, we lost the object in SVN and the history of it.

    You need to found a workaround like Rename _DROP

    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)

    Dropped objects are no longer in the latest version in source control, but they are still in the previous versions. In SVN, if you “show log,” on the directory level, you should be able to find the dropped object. You can right-click on it and “show log” again to get the entire history for that dropped object.

  5. My work has an internet proxy server that filters connections. When the reporting tool asked to send crash report it failed because proxy server wasn't specified. Any way to configure this?

    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)
  6. SSMS 2008 hung after upgrading to 0.2.1.1. I had to kill the task. I started SSMS 2005, which opened normally. Then, I reopened SSMS 2008 and it started normally.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    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)
  7. Just wondered if someone could explain what the following query has to do with source code control in a Database.

    SET XACTABORT ON ;

    DECLARE @defaultTraceFileName NVARCHAR(256);

    SELECT @defaultTraceFileName = CONVERT(NVARCHAR(256), value)

    FROM fn
    trace_getinfo(DEFAULT)

    WHERE [property] = 2

    AND value IS NOT NULL;

    SELECT
    dt.StartTime
    , dt.DatabaseID
    , dt.TransactionID
    , dt.EventSubClass
    , dt.EventClass
    , dt.ObjectID
    , sysTSV.subclassname AS ObjectType
    , CONVERT(NVARCHAR(256), NULL) AS SchemaName
    , dt.ObjectName
    , dt.LoginName
    , dt.ApplicationName

    FROM ::fn
    tracegettable(@defaultTraceFileName, default) AS dt
    LEFT JOIN sys.trace
    subclassvalues AS sysTSV
    ON sysTSV.trace
    eventid = dt.EventClass
    AND sysTSV.subclass
    value = dt.ObjectType
    WHERE dt.EventSubClass…

    1 vote
    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)
  8. While attempting to Create new link to source control in SSMS 2008 I receive the following message: "The URI needs to be an empty directory."
    How can I resolve this?

    Please advise..
    Brett

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  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)
  9. 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)
  10. So, this is bad development, but someone put a proc named dbo.USPEmp#. I get all sorts of errors now because of the # sign in the when getting latest updates or trying to delete and commit.

    Failed to update:

    oEc.#8Jf: Errors occured whilst parsing file C:\Users\adamr\AppData\Local\Red Gate\SQL Source Control 0\WorkingBases\b3ae1b30-6f18-4d35-a002-1daa9b3501b5\Stored Procedures\dbo.uspEmp#.sql

    'line 5:34: unexpected token: ["#",<735>,line=5,col=34] [char=85]'
    ---> #Eyg.#Lyg: Errors occured whilst parsing file C:\Users\adamr\AppData\Local\Red Gate\SQL Source Control 0\WorkingBases\b3ae1b30-6f18-4d35-a002-1daa9b3501b5\Stored Procedures\dbo.uspEmp#.sql
    'line 5:34: unexpected token: ["#",<735>,line=5,col=34] [char=85]'
    ---> line 5:34: unexpected token: ["#",<735>,line=5,col=34] [char=85]
    --- End of inner exception stack trace ---
    at #oEc.#7Jf.#t.#B3.#sKf()
    at #oEc.#7Jf.#gKf(Action action)
    --- End of inner…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    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)
  11. it be very usful to add comments when commiting changes - so we can see why a certain changes were made

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    There is a 1 line comment box at the top of the “Commit Changes” tab for your comment. If you have a SVN Hook set up to require comments, then your commit will fail unless a comment is entered.

  12. 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)
  13. 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.

  14. I wanted to test rebuilding my DB from nothing but when I created a new DB with the same name as the old one, SQL source control showed it as already linked (odd but not a problem) but then it told me there were no changes to get and it wanted to commit a drop of everything!

    I worked around it by naming the new DB something different

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

  16. When committing large numbers of changes under CVS, the commit fails with error message 'command line too long'.

    1 vote
    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. On the Commit Changes and Get Lastest tab, you should include the last user that modified the object. Far too many times I have to ask all the developers to identify the objects that they have changed yet not committed. It would be nice to be able to see that.

    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)
  18. the option seems to have been removed in Source Control 2, we really found this a helpfull option so we wonder why is was removed.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    There’s only 1 link, but it can do either. If you link to an empty folder, then that’s like a “new” link. If you link to a folder that contains a RedGate.ssc file, then that will link to the existing repository location. :-)

  19. The browse button makes using the product so much easier. Thanks for adding it.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    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)
  20. I accidentally tripped over the right click menu that allows you to edit filter rules after trying earlier in the day to find it and giving up. Suggest adding a button to the UI so it is more obvious.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    As of SQL Source Control 3.8.11, you can access the ‘Edit Filter Rules’ option from a few places:

    • A button on the Setup tab, under “Options just for this database”
    • Through the right click menu in the Management Studio Object Explorer
    • Through the right click menu on the SQL Source Control changes list
  • Don't see your idea?