179 results found

1. Bug: Changes detected after commit

   There are changes detected to a table in the commit screen, but the details show no changes - even after committing this phantom change, the commit screen still shows that table having changes pending. v3.5.6.338 standard. A few things to note about the table that might help to resolve: The table is a partitioned table, with a Geography data type in it, and also has a ColumnStore index.

   10 votes

   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  ·  fiona.gazeley responded

   Closing this as it looks like SQL Compare now supports ColumnStore indexes

2. "Failed to update" message after encountering a ";" in a stored procedure

   Ran into an issue when entering a stored procedure with a semi colon in it.

   Failed to update:

   oEc.#8Jf: Errors occured whilst parsing file C:\Documents and Settings\Adam\Local Settings\Application Data\Red Gate\SQL Source Control 0\WorkingBases\4c857d86-7cf5-464b-86bc-01d4f22d1423\Stored Procedures\Article.GetArticlesByKewords.sql

   'line 47:2: unexpected token: [";",<631>,line=47,col=2] [char=1276]'
   ---> cZ: Errors occured whilst parsing file C:\Documents and Settings\Adam\Local Settings\Application Data\Red Gate\SQL Source Control 0\WorkingBases\4c857d86-7cf5-464b-86bc-01d4f22d1423\Stored Procedures\Article.GetArticlesByKewords.sql
   'line 47:2: unexpected token: [";",<631>,line=47,col=2] [char=1276]'
   ---> line 47:2: unexpected token: [";",<631>,line=47,col=2] [char=1276]
   --- 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)

   For your information, the following is the text in the stored procedure....

   -- =============================================
   
   -- Author: <Chandrashekar>
   
   -- Create date: <10 Jun 2009>
   
   -- Description: <Get Articles By Kewords and Section >
   
   -- =============================================
   
   CREATE Procedure [Article].[GetArticlesByKewords]
   
   (
   
   @Keywords varchar(max) = '',
   
   @Section varchar(50) = Null,
   
   @ArticleId int = Null, --For Suppressing Articles
   
   @CountID int = Null,
   
   @IncludeDeleted bit = 0
   
   )
   
   As
   
   /*
   
   SELECT
   
   distinct c.contentid as contentid,
   
   c.titlebox1 as title,
   
   c.section as section,
   
   c.keywords as keyword,
   
   c.priority as priority,
   
   article.section.SectionName as description
   
   FROM
   
   content c
   
   CROSS APPLY dbo.Csvtovarchar(@Keywords) r
   
   INNER JOIN content On c.keywords LIKE '%' + r.VarCharValue + '%'
   
   INNER JOIN article.section ON article.section.SectionCode =c. section-- @Section
   
   WHERE c.contenttype='ARTICLE'
   
   AND
   
   (
   
   (@Section IS NULL )OR
   
   (@Section IS NOT NULL AND c.section LIKE '%' + @Section + '%' )
   
   )

   AND
   
   (
   
   (@ArticleId IS NULL )OR
   
   (@ArticleId IS NOT NULL AND c.contentid <> @ArticleId )
   
   ) */

   ;

   With cte (rank,contentid,title,section,keyword,priority,description)
   
   As (
   
   SELECT
   
   --row_number() Over(Order by c.priority),
   
   rank() Over(Order by c.contentid ),
   
   c.contentid as contentid,
   
   c.titlebox1 as title,
   
   c.section as section,
   
   c.keywords as keyword,
   
   c.priority as priority,
   
   article.section.SectionName as description
   
   FROM
   
   content c
   
   CROSS APPLY dbo.Csvtovarchar(@Keywords) r
   
   --INNER JOIN content On c.keywords LIKE '%' + r.VarCharValue + '%'
   
   INNER JOIN article.section ON article.section.SectionCode = c. section-- @Section
   
   WHERE c.contenttype='ARTICLE'
   
   And c.keywords LIKE '%' + r.VarCharValue + '%'
   
   AND
   
   (
   
   (@Section IS NULL )OR
   
   (@Section IS NOT NULL AND c.section LIKE '%' + @Section + '%' )
   
   )

   AND
   
   (
   
   (@ArticleId IS NULL )OR
   
   (@ArticleId IS NOT NULL AND c.contentid <> @ArticleId )
   
   )
   
   And
   
   (
   
   (@IncludeDeleted = 1) Or
   
   (c.priority > 0)
   
   )
   
   )
   
   Select Distinct
   
   contentid, title, section, keyword, priority, description
   
   FROM CTE
   
   Where (@CountID Is Null) Or (@CountID >= rank)

   Looking at the procedure, it shouldn't have a semi colon where it does, but still I would expect the application to be able to handle it.

   Ran into an issue when entering a stored procedure with a semi colon in it.

   Failed to update:

   oEc.#8Jf: Errors occured whilst parsing file C:\Documents and Settings\Adam\Local Settings\Application Data\Red Gate\SQL Source Control 0\WorkingBases\4c857d86-7cf5-464b-86bc-01d4f22d1423\Stored Procedures\Article.GetArticlesByKewords.sql

   'line 47:2: unexpected token: [";",<631>,line=47,col=2] [char=1276]'
   ---> cZ: Errors occured whilst parsing file C:\Documents and Settings\Adam\Local Settings\Application Data\Red Gate\SQL Source Control 0\WorkingBases\4c857d86-7cf5-464b-86bc-01d4f22d1423\Stored Procedures\Article.GetArticlesByKewords.sql
   'line 47:2: unexpected token: [";",<631>,line=47,col=2] [char=1276]'
   ---> line 47:2: unexpected token: [";",<631>,line=47,col=2] [char=1276]
   --- 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[]… more

   9 votes

   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

   This has been fixed in EA2 (v0.2.1), which was released on Mon 22 Feb 2010.

3. Setup tab link URL should be selectable

   The link text on the setup tab should be selectable. It would be an easy change, and when you're creating a new database from the source you don't have to look up the URL somewhere else if you want to "clone" a database.

   9 votes

   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…)
   5 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  ·  AdminChris Smith (Project Manager - SQL Lighthouse, Redgate) responded

   If you right click on the URL on the Setup tab, you can copy it. I know this is kind of hidden. This works for both SVN and TFS.

4. Show or Filter By User who last updated on Commit List for Shared (Centralized) DB Model

   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 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  ·  Better Support for Shared Db Dev Model  ·  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 feature is included in SQL Source Control v2.0, http://www.red-gate.com/MessageBoard/viewtopic.php?t=12947.

   If you setup your database as shared, then you will see who last updated each object on the Commit tab and Undo dialog. Only objects that you last updated will be checked by default.

   NOTE: Databases linked in v1 default to dedicated databases. You will need to relink your databases to switch development models.

5. log files

   The log files at

   C:\Users<user>\AppData\Local\Red Gate\Logs\SQL Source Control 3

   can completely consume the free space on my C drive within a day. I have watched the files in this folder grow to 10gb in an afternoon.

   How do I turn these off or set a size limit. I would also like to move them to a different location.

   8 votes

   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…)
   11 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  ·  AdminChris Smith (Project Manager - SQL Lighthouse, Redgate) responded

   SQL Source Control v3.0.5.7 has been released and should have resolved the excessive logging in the product.

   To get this version, please run Check For Updates from the Help menu in SQL Source Control. This is a free upgrade for existing licensed v3 users and for users with a Support & Upgrades contract.

6. Have an option to ignore Extended Properties

   Is there an option to ignore extended properties

   7 votes

   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  ·  AdminChris Smith (Project Manager - SQL Lighthouse, Redgate) responded

   SQL Source Control v3.0.5.7 includes a mechanism to allow comparison options to be configured, including ‘Ignore Extended Properties’. To get this version, please run Check For Updates from the Help menu in SQL Source Control.

   Comparison options can now be set via a configuration file in your database repository’s Working Base folder. The following article describes how to configure this option: http://www.red-gate.com/SupportCenter/GeneralContent/knowledgebase/SQL_Source_Control/KB201202000521

   Our plan in the future is to provide an options dialog to allow users to configure the comparison options that are changed most often, but we believe this configuration file procedure should help users in the interim.

   If you’d like to see an options dialog exposing these settings in SQL Source Control, please vote on the following idea – https://redgate.uservoice.com/admin/forums/39019-sql-source-control/suggestions/2615460-add-an-options-dialog-to-allow-configuration-of-co – and let us know which options you’d like to see exposed in the dialog.

7. Migration script name patterns

   The pattern for migration script names should be a configuration. I would like my migration scripts to identify the version of the database instead of the revisions. Thus I would like to define the name of the migration script.

   7 votes

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

   The ability to name migration scripts is now available in SQL Source Control v3.4. For details and to download, please see http://documentation.red-gate.com/display/SOC3/Release+notes+and+other+versions.

   We have also been working on v2 of Migrations. An Early Access Release of SQL Source Control is now available with Migrations v2. To download, please see http://documentation.red-gate.com/display/MV2.

   NOTE: This is an Early Access Release and is not fully tested or functionally complete yet. It would be great if you could try it in a test environment and let us know about your experiences so we can fix any issues and try to make any updates you need before the full release.

   Thank you!
   Stephanie Herr :-)

8. Changes to dbo schema can't commit

   After granting the dbo schema rights to a userdefined role I can't commit it

   6 votes

   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

   This has been fixed in the latest release.

   Thank you!

9. SQL Source Control won't stay docked

   Upon opening SSMS, SQL Source Control always starts up as a tabbed document. I always (re-)dock it, but it doesn't remember that preference.

   6 votes

   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 completed in EA6 (v0.3.3.1), which was released on May 6th. Please let us know if you experience any issues with your docking.

10. Is "schema.Load" as a table name causing an error?

    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 you want it)

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

    6 votes

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

    This has been fixed in the latest version of SQL Source Control.

11. Failed to update An item with the same key...

    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: SmartExceptionsCore.UnhandledException @ 256, offset:38 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1730, offset:0 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 255, offset:30 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 258, offset:38 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 836, offset:61 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 822, offset:89 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 834, offset:14 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1901, offset:31 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1718, offset:63 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 188, offset:468 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1896, offset:1011 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1734, offset:18 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 256, offset:38 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 260, offset:38 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1570, offset:224 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1893, offset:63 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1569, offset:99 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1568, offset:60 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1105, offset:31 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1102, offset:0 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1809, offset:0 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1720, offset:117 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 171, offset:11 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 218, offset:137 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 522, offset:26 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1939, offset:18 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1733, offset:32 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1734, offset:36 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1891, offset:43 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1192, offset:500 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1196, offset:109 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1198, offset:22 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1147, 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 ---
    --- 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 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)

    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:

    … more
    6 votes

    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 has been fixed in v1.0. Please contact support@red-gate.com, if you are still experiencing any problems.

    Thank you!

12. SQL Source Control wont stop reporting geometry objects changed.

    It keeps saying these need to be 'commited', even though they are up to date.

    ALTER TABLE [dbo].[Cities] ADD CONSTRAINT [enforcesridgeometryCity] CHECK (([STSrid]=(0)))
    ALTER TABLE [dbo].[Cities] ADD CONSTRAINT [enforcesridgeometryCity] CHECK (([geom].[STSrid]=(0)))

    Table recreation code.

    CREATE TABLE [dbo].[Cities](
    [CityID] [int] IDENTITY(1,1) NOT NULL,
    [State] [char](2) NULL,
    [StateID] [int] NULL,
    [Name] [nvarchar](255) NULL,
    [LSAD] [tinyint] NULL,
    [LSADTRANS] [nvarchar](16) NULL,
    [geom] [geometry] NULL,
    CONSTRAINT [PKCityF2D21A9643D61337] PRIMARY KEY CLUSTERED
    (
    [CityID] ASC
    )WITH (PADINDEX = OFF, STATISTICSNORECOMPUTE = OFF, IGNOREDUPKEY = OFF, ALLOWROWLOCKS = ON, ALLOWPAGE_LOCKS = ON) ON [PRIMARY]
    ) ON [PRIMARY]

    GO

    SET ANSI_PADDING OFF
    GO

    ALTER TABLE [dbo].[Cities] WITH CHECK ADD CONSTRAINT [enforcesridgeometry_City] CHECK (([geom].[STSrid]=(0)))
    GO

    ALTER TABLE [dbo].[Cities] CHECK CONSTRAINT [enforcesridgeometry_City]
    GO

    It keeps saying these need to be 'commited', even though they are up to date.

    ALTER TABLE [dbo].[Cities] ADD CONSTRAINT [enforcesridgeometryCity] CHECK (([STSrid]=(0)))
    ALTER TABLE [dbo].[Cities] ADD CONSTRAINT [enforcesridgeometryCity] CHECK (([geom].[STSrid]=(0)))

    Table recreation code.

    CREATE TABLE [dbo].[Cities](
    [CityID] [int] IDENTITY(1,1) NOT NULL,
    [State] [char](2) NULL,
    [StateID] [int] NULL,
    [Name] [nvarchar](255) NULL,
    [LSAD] [tinyint] NULL,
    [LSADTRANS] [nvarchar](16) NULL,
    [geom] [geometry] NULL,
    CONSTRAINT [PKCityF2D21A9643D61337] PRIMARY KEY CLUSTERED
    (
    [CityID] ASC
    )WITH (PADINDEX = OFF, STATISTICSNORECOMPUTE = OFF, IGNOREDUPKEY = OFF, ALLOWROWLOCKS = ON, ALLOWPAGE_LOCKS = ON)… more

    6 votes

    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 has been fixed in v1.0. If you are still having a problem with this issue, then please contact support@red-gate.com.

13. Support CVS as a source control system

    I do not want to switch to SVN or TFS. I'm already using CVS and it would be great if SQL Source Control would support CVS.

    6 votes

    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

    The new 2.0.3 Early Access build now supports source controlling your databases with CVS.

    To get the new Early Access release please visit the following link:

    https://www.surveymk.com/s/SqlSourceControl_EapSignup

    Please note that we don’t support accessing the history directly from within SSMS when using CVS.

14. Bazaar VCS

    Can you consider implementing support for Bazaar VCS? Thanks!

    6 votes

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

    The new 2.0.3 Early Access build now supports source controlling your databases with Bazaar.

    To get the new Early Access release please visit the following link:

    https://www.surveymk.com/s/SqlSourceControl_EapSignup

    Please note that we don’t support accessing the history directly from within SSMS when using Bazaar.

15. Support for SQL Server 2019 Inline function syntax

    SQL server 2019 new syntax, for instance for inline functions, is not supported by Redgate Source Control. Could you please add that support? There is another user with the same problem as described here.

    Thanks in advance.
    Best,
    Jose.

    6 votes

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

    Support for the inline function syntax has been released in SQL Compare v 15.2.5.  You can get the latest version at https://www.red-gate.com/products/sql-compare.

16. Checking checks/unchecks all items...how about just the one I selected?

    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 selected. It's like being in Windows Explorer, selecting a bunch of files then clicking one of those files...you don't expect ALL of those files to suddenly deselect (well they do but only because you're now looking at a single selection...the one you clicked). If you hold the shift-key down, it just toggles the one selection. If you don't, it still toggles selections...it removes all selections but the one you've selected.

    You either need to make a click on a particular row affect that row only (just like if I select any other part of the row selects that row only) or you need to let it just toggle the checkbox if that's what I clicked.

    It took me a second to figure out...I was amazed that someone would even think to make a single click on a single row affect an entire selection of rows...

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

    5 votes

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

17. Automatically Generate migration script

    Here is the scenario I going about. During iteration several developer does their check-ins and they do not create a migration script since then on Databases. But when it time to push build its a pain to go back to previous version of database and generate migration script using SQL Compare. Can't we have an option to generate a script right from SSMS by doing a diff between the two checked in revision in version control. Also another idea may be to allow create snapshot right from SSMS and developer can generate a script from that snapshot. We can have some manual process to achieve this but y not have a integrated solution to this problem.

    Here is the scenario I going about. During iteration several developer does their check-ins and they do not create a migration script since then on Databases. But when it time to push build its a pain to go back to previous version of database and generate migration script using SQL Compare. Can't we have an option to generate a script right from SSMS by doing a diff between the two checked in revision in version control. Also another idea may be to allow create snapshot right from SSMS and developer can generate a script from that snapshot. We can have… more

    5 votes

    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

    The SSMS Integration Pack, which comes with SQL Compare Pro 8.50, can generate migration scripts between 2 versions in source control. For more information, please see http://www.red-gate.com/supportcenter/Content.aspx?p=SQL%20Compare&c=SQL_Compare/help/8.50/ssmsip_deploy_soc.htm&toc=SQL_Compare/help/8.50/toc1280663.htm.

18. Handle Getting New NOT NULL Columns

    In a dedicated development model where each developer works against their own copy of the db, if my co-worker adds a new NOT NULL column to a table, the get latest script will fail for me since my table contains data and NULLS are not allowed in this new column.

    Please comment on how you would like to see us handle this?

    5 votes

    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  ·  AdminChris Smith (Project Manager - SQL Lighthouse, Redgate) responded

    SQL Source Control 3.0 is now available!

    It includes a new feature called ‘Migrations’ that will help avoid data loss when adding a NOT NULL column as it allows you to create, store and share SQL change scripts for accurate deployment.

    For more information about Migrations, please visit:
    http://www.red-gate.com/supportcenter/Content/SQL_Source_Control/help/3.0/SSC_Working_With_Migrations

19. Regular Expressions in Filter

    When setting up filter rules, it would be useful if we could use some regular expressions on the criteria. We have several objects that we would like to exclude from source control when they end with a string of 6 numbers. The numbers are different for each object, so if we could use some simple regular expressions, we could filter out objects that end with [0-9][0-9][0-9][0-9][0-9][0-9].

    5 votes

    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  ·  Gareth Bragg responded

    As of SQL Source Control 3.8.13, filter rules now support the standard T-SQL LIKE syntax for wildcard characters (‘%’, ‘_’, ‘[abc]’, and ‘[^abc]’ – see MSDN for details).

    To include wildcard characters explicitly in a filter, they can be escaped with square brackets.

    ‘Equals’ and ‘Does not equal’ operators will not treat those characters as special wildcard characters.

20. Very easy to use and install

    I think this product is brilliant and delivers simple version control for databases - something that has always been lacking. I do agree though that it would be nice to have more SVN options via the SQL Server interface

    4 votes

    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…