179 results found

1. "create to new link to source control" link not enabled

   can't set up my link to the source control:

   http://i.imgur.com/Uy7wY.jpg

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  AdminRedgate Administrator (Admin, Redgate) responded

   The links are disabled until a user selects a database in Object Explorer.

2. BUG: Objects with extended properties can't be committed

   When adding extended properties to tables (like an svn keyword) it fails to commit

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  AdminRedgate Administrator (Admin, Redgate) responded

   We think this issue has been fixed in v1.0. If you are still experiencing any problems, please contact support@red-gate.com.

3. Thank you!

   http://www.youtube.com/watch?v=DpJyG7B6tAI

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  AdminRedgate Administrator (Admin, Redgate) responded

   Thanks for your feedback! It’s great to hear! :-)
   I’m closing this suggestion so you can have your votes back…

4. Error Linking to a DB already in source control

   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 @ 210, offset:30 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 213, offset:38 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 773, offset:61 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 757, offset:31 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 771, offset:14 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1514, offset:36 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1357, offset:63 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 165, offset:468 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1507, offset:800 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1373, offset:18 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 211, offset:38 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 215, offset:38 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1205, offset:143 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1204, offset:6 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 958, offset:31 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 957, offset:0 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1455, offset:0 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1359, offset:117 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 149, offset:11 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 186, offset:137 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 930, offset:22 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1633, offset:31 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1002, offset:500 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1006, offset:109 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1008, offset:22 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1010, offset:13

   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   at #oEc.#7Jf.#t.#B3.#sKf()
   at #oEc.#7Jf.#gKf(Action action)
   --- End of inner exception stack trace ---

   Server stack trace:
   at #eEc.#fEc.#t.#izb.#j5f()
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)

   Exception rethrown at [0]:
   at RedGate.SQLSourceControl.CommonUI.Forms.ErrorDialog.DoWithObviousExceptionsThrowAll(Action action)
   at #JLc.#PLc.#CTc(ICancellableOperation`1 operation, Object token)

   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 @

   … more
   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  AdminRedgate Administrator (Admin, Redgate) responded

   This has been fixed in v1.0. (SOC-594)

5. Many Conflicts in GetLatest and Commit tab pages

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

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  AdminRedgate Administrator (Admin, Redgate) responded

   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!

6. Drop object should not be drop from SVN

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

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  AdminRedgate Administrator (Admin, Redgate) responded

   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.

7. Proxy server option

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

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  AdminRedgate Administrator (Admin, Redgate) responded

   Unfortunately, this cannot be configured at this time, but if sending fails, you can save the report to your computer and then email it to Support@red-gate.com.

   Thank you!

8. 0.2.1.1 Hangs SSMS 2008

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

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  AdminRedgate Administrator (Admin, Redgate) responded

   This has been fixed in v1.0.

9. Question about Trace query being run

   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 fntrace_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 ::fntracegettable(@defaultTraceFileName, default) AS dt
   LEFT JOIN sys.tracesubclassvalues AS sysTSV
   ON sysTSV.traceeventid = dt.EventClass
   AND sysTSV.subclassvalue = dt.ObjectType
   WHERE dt.EventSubClass IN ( 0, 1 )
   AND dt.EventClass IN ( 46, 47, 164 )
   AND sysTSV.subclass_name IN ('ST', 'AS', 'BN', 'CT', 'EN', 'IX', 'MT', 'PF', 'PS', 'RT', 'SC', 'SV', 'SX', 'TA', 'TR', 'U' );

   This was part of a lot more convoluted and overly complex query that was captured while profiling a server that I'm testing SQL Source Control on.

   The resultset from this query generated over 30K rows and only a very few related to the database that was under source control.

   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 fntrace_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 ::fntracegettable(@defaultTraceFileName, default) AS dt
   LEFT JOIN sys.tracesubclassvalues AS sysTSV
   ON sysTSV.traceeventid = dt.EventClass
   AND sysTSV.subclassvalue = dt.ObjectType
   WHERE dt.EventSubClass… more

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  AdminRedgate Administrator (Admin, Redgate) responded

   I think the procedure has changed slightly, but it’s used to identify changes to your database to put blue indicators on your Object Explorer.

10. The URI needs to be an empty directory

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

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    completed  ·  2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. on new version installation, it closes sql server management studio without asking

    subj

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  AdminRedgate Administrator (Admin, Redgate) responded

    This fix is included in SQL Source Control v2.0, http://www.red-gate.com/MessageBoard/viewtopic.php?t=12947.

12. Bug - Bad object names causes error (Obj name contains #)

    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 exception stack trace ---

    Server stack trace:
    at RedGate.SQLSourceControl.Engine.Cancellables.CancellableOperation.#t.#izb.#j5f()
    at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
    at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
    at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)

    Exception rethrown at [0]:
    at RedGate.SQLSourceControl.CommonUI.Forms.ErrorDialog.DoWithObviousExceptionsThrowAll(Action action)
    at #JLc.#PLc.#CTc(ICancellableOperation`1 operation, Object token)

    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… more

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  AdminRedgate Administrator (Admin, Redgate) responded

    This is fixed in v1.0.

    Thanks for your help!
    Stephanie M. Herr
    SQL Source Control – Project Manager

13. ability to add comments when commiting changes

    it be very usful to add comments when commiting changes - so we can see why a certain changes were made

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  AdminRedgate Administrator (Admin, Redgate) responded

    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.

14. Bug: partition function gives error when adding to SQL Source Control.

    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 #Eyg.#Gyg.#vl()
    at RedGate.SQLCompare.Engine.Database.Register(String path, ScriptDatabaseInformation dbinfo, Options options)
    at #G3c.#L3c.#t.#u3.#i4c()
    at #oEc.#7Jf.#hKf(ICancellableOperationStatus status, ICancellable database, Action action)
    at #oEc.#7Jf.#t.#B3.#sKf()
    at #oEc.#7Jf.#gKf(Action action)
    --- End of inner exception stack trace ---

    Server stack trace:
    at #oEc.#7Jf.#gKf(Action action)
    at #oEc.#7Jf.#jKf(ICancellableOperationStatus status, ICancellable database, Action action)
    at #G3c.#L3c.#e4c(String path, #M3c args)
    at #G3c.#K3c.#83c(String path, TArg argument)
    at #G3c.#L3c.#f6c(String path, ScriptDatabaseInformation folderOptions, Options options, ICancellableOperationStatus status)
    at #oEc.#i7c.#t.#9Jf.#t.#2Db.#TSi()
    at RedGate.SQLSourceControl.Engine.Cancellables.CancellableOperation.#t.#izb.#j5f()
    at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
    at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
    at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)

    Exception rethrown at [0]:
    at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
    at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
    at RedGate.SQLSourceControl.Engine.Action.EndInvoke(IAsyncResult result)
    at RedGate.SQLSourceControl.Engine.Cancellables.CancellableOperation.#zIc(ICancellableOperationStatus status, Pair2[] labelledActions)
at #oEc.#i7c.#t.#9Jf.#SSi()
at #oEc.#7Jf.#t.#9Jf.#uKf()
at #oEc.#7Jf.#hKf(ICancellableOperationStatus status, ICancellable database, Action action)
at #oEc.#7Jf.#lKf[T](ICancellableOperationStatus status, ICancellable database, Func1 function)
    at #oEc.#i7c.#QSi[TDiffType](ICancellableOperationStatus status, IReadOnlySourceControlServerCallBacks sourceControlUserCallBacks, ScriptDatabaseInformation folderOptions)
    at #oEc.#i7c.#t.#z2.#hOi()
    at #oEc.#i7c.#bOi[TDiffType](ICancellableOperationStatus status, Func1 innerBuild)
at #oEc.#i7c.#q1f(ICancellableOperationStatus status, IReadOnlySourceControlServerCallBacks sourceControlUserCallBacks, ScriptDatabaseInformation folderOptions)
at #oEc.#4Ec.#z7c(ICancellableOperationStatus status, IReadOnlySourceControlServerCallBacks sourceControlUserCallBacks)
at #oEc.#4Ec.#7Jc(ICancellableOperationStatus status, IReadOnlySourceControlServerCallBacks sourceControlUserCallBacks)
at #oEc.#4Ec.#t.#A2.#D7c(ICancellableOperationStatus status)
at #eEc.#iEc.#t.#u3.#k5f()
at RedGate.SQLSourceControl.Engine.Cancellables.CancellableOperationBase.InvokeWithTracker(Action action)
at #eEc.#iEc.Invoke()
at #JLc.#Qlg.Invoke()
at #mMc.#8Ec.#t.#57c.#l8i()
at #mMc.#8Ec.#LBf(Action action)
at #mMc.#8Ec.#LBf[T](Func1 action)
    at #JLc.#PLc.#t.#Jfb.#EJf()
    at RedGate.SQLSourceControl.Engine.SmartAssembly.ExceptionReporting.ErrorReporterBase.#Mwf(Action toDo, Predicate1 shouldReportPredicate)
at RedGate.SQLSourceControl.Engine.SmartAssembly.ExceptionReporting.ErrorReporterBase.Do(Action toDo, Predicate1 shouldReportPredicate, Boolean rethrow)
    at RedGate.SQLSourceControl.Engine.SmartAssembly.ExceptionReporting.ErrorReporterBase.DoWithObviousExceptionsRethrowAll(Action action)
    at RedGate.SQLSourceControl.CommonUI.Forms.ErrorDialog.DoWithObviousExceptionsRethrowAll(Action action)
    at #JLc.#PLc.#CTc(ICancellableOperation`1 operation, Object token)

    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… more

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  AdminRedgate Administrator (Admin, Redgate) responded

    This has been fixed in the latest release. Please let us know if you are still having problems.

15. Funny bug: Keep mine not working

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

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    3 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  AdminRedgate Administrator (Admin, Redgate) responded

    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.

16. Rebuilding a DB - bug?

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

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. 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 Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Support Additional Source Control Systems  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    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.

18. Committing large number of changes on CVS fails

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

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  Gyorgy Pocsi responded

    Fixed in EA version 2.0.3.13. You can get the latest EA version from https://www.surveymk.com/s/SqlSourceControl_EapSignup

19. Add Last User Modified

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

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  AdminRedgate Administrator (Admin, Redgate) responded

    In v2, when you are working on a shared model, we show who has changed the object in the database on the Commit tab. We also only check your own changes by default.

    If you would also like to see the last person who committed when you Get Latest, please vote/comment on http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/1375333-show-who-committed-the-changes-in-the-get-latest-l.

20. Link to a database already in source control

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

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  AdminRedgate Administrator (Admin, Redgate) responded

    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. :-)