179 results found

1. Detect the right order to commit changes
   3 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…)
   4 comments  ·  Initial Setup  ·  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

   There was a bug in the first EA, which caused problems when trying to do the initial commit for large number of objects. It’s now fixed, please get the latest version.

2. Make RedGateDatabaseInfo.xml easier to merge

   When we look at the RedGateDatabaseInfo.xml file, it appears as one long line of text. Merging this is nigh on impossible because the one line conflicts. It would be nice if it was written in a pretty xml format to help with merging

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

   Form Source Control version 2.1, RedGateDatabaseInfo.xml should now be in a more structured format.

   Please comment on this suggestion if this new structure does not meet your requirements.

   Please visit our product page for more information on the latest version of SQL Source Control:
   http://www.red-gate.com/products/sql-development/sql-source-control/

3. Doesn't support views with schemabinding on

   We have views with schemabinding set to true in SQL2008, SQL Source Control does not recognize that there is a dependency and throws and error.

   3 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  ·  James Billings responded

   Having tested this out, the product does handle the schemabinding option on views. If a table needs to be rebuilt, it will alter the view to remove the schemabinding, update the table, then alter the view again to put the setting back.

   The specific problem here was unable to be determined after following up with Nick and may have just been a one-off.

4. Clean up temporary TFS workspaces when using sql compare

   Apparently SSC creates temporary workspaces when being called from SQL Compare (when using a source controlled version of the database as the source of the comparison), but it doesn't seem to clean up after itself completely. When I go to manage my workspaces in TFS, it is currently showing that I have over 50 temporary workspaces that were created by SSC. I can't swear to it, but I think this may have caused issues with our builds, as I have observed at one point that I inadvertently checked code files out to one of these temporary workspaces instead of my default workspace. I think this needs to be addressed. I would almost categorize it as a bug.

   Apparently SSC creates temporary workspaces when being called from SQL Compare (when using a source controlled version of the database as the source of the comparison), but it doesn't seem to clean up after itself completely. When I go to manage my workspaces in TFS, it is currently showing that I have over 50 temporary workspaces that were created by SSC. I can't swear to it, but I think this may have caused issues with our builds, as I have observed at one point that I inadvertently checked code files out to one of these temporary workspaces instead of my… more

   3 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 3.0 is now available which includes a fix for this issue.

   TFS workspaces are created when linking to a database in SQL Source Control – from v3.0 these are deleted when the database is unlinked.

   To download v3, please visit:
   http://www.red-gate.com/products/sql-development/sql-source-control/

5. Support Getting Latest Migration Scripts

   According to Red Gate support, migration scripts only run when using SQL Compare, not when using Get Latest within SQL Source Control. Therefore if I have data, real or test, in every development instance, the Get Latest tab is useless in the product and I must use SQL Compare to deploy the changes. I can't imagine it would be too difficult to just run the migration script when using Get Latest.

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

   Migration scripts are used in SQL Source Control when Getting Latest. Once you click on the “Get Latest” button, you should recieve a warning about the migration script. If it fails, there will be an option to edit the script it was trying to run. The best thing to do is review the script and execute it in SSMS. If there’s an error, it may be a syntax error within the migration script. Once it is corrected, you can execute the script, then refresh the Get Latest tab and you should be in synch.

   I’m sorry about the confusion.

6. Intellisense when typing table with underscores (My_Table)

   I have a table called My_Table.

   I should be able to just type "mytab" and have Sql prompt recognize that as an option in intellisense, like devart SQL Complete does. Currently, it gives me no suggestions.

   3 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

   This was fixed in version 6. Typing a table name without underscores will show suggestions for matching table names with underscores.

7. Migrations from Working Folder link

   In the "Link to source control" screen there are a number of options.

   We use branches, so our working folder is always the most relevant to what we are doing.

   When we point the link to the WorkingFolder, everything is great, however, the "Migrations" tab is not available for this type of connection.

   This is a pity, because we need to create a migration script that will update the main trunk, when we merge our branch back in.

   Please enable the Migrations feature for the "Workingfolder" type of link.

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

   I am delighted to let you know that this is now released! You can now create migrations scripts even when you’re using working folders.

   If you don’t have SQL Source Control installed, you can download it from http://www.red-gate.com/products/sql-development/sql-source-control/.

   If you already have SQL Source Control you can get the new version via Check for updates in the Help menu of SQL Source Control inside SSMS.

   You can see other Migrations examples and tutorials here: https://documentation.red-gate.com/display/SOC5/Migration+script+examples

   Thank you for sticking with us while we worked on this, and please keep the feedback coming!

8. To be able to configure the default behavior of the 'Include Dependencies' check box

   When committing changes to source control, the 'Include Dependencies' check box is set to true. Can this default behavior be changed to false?
   OR
   Can the user have the option to set the default behavior?

   3 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  ·  James Billings responded

   The latest frequent-update version of SQL Source Control (4.0.6.179) allows you to default the checkbox behaviour to off. To do this, you’ll need to edit your UI Options file (RedGate_SQLSourceControl_CommonUI_UIOptions.xml) which you’ll find in localappdata\Red Gate\SQL Source Control 4 and add a tag called IncludeDependenciesCheckbox, like this:

   False

   If the value is false, then the checkbox will be un-set by default.

9. Show server name in main window

   My databases have the same name on the production server, the dev server and my local machine.

   Sadly Source Control shows me only the database name in the upper right conor of its main window. And because there is neither a status bar nor the server name in the tab name, I'm often unsure which database exactly it compares at the moment.

   PS: I know, it is the one with the one with the light-gray-on-white-background in the object explorer, if I scoll up to the database level, but the scrolling is annoying and I have to look twice to see the light gray on white...

   My databases have the same name on the production server, the dev server and my local machine.

   Sadly Source Control shows me only the database name in the upper right conor of its main window. And because there is neither a status bar nor the server name in the tab name, I'm often unsure which database exactly it compares at the moment.

   PS: I know, it is the one with the one with the light-gray-on-white-background in the object explorer, if I scoll up to the database level, but the scrolling is annoying and I have to look twice to see… more

   3 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  ·  James Billings responded

   This should be available in our next frequent channel update (on/after August 19).

10. Where are the credentials coming from?

    After I connect to a database, everything works very intuitively. In fact it's so intuitive that I see my account used for commits, but I'm not sure where it found my login credentials. Is there a way to use a different set of credentials if you have multiple svn accounts?

    2 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…)
    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

11. Crash (unrecoverable) after checking in some objects, but not dependencies

    Message shown after Registering Live Database stage of refreshing display.

    Failed to update:

    oEc.#8Jf: Failed to locate the target table [dbo].[tbNMI] for the FKtbNMINSRDtbNMI foreign key. ---> RedGate.SQLCompare.Engine.SqlCompareException: Failed to locate the target table [dbo].[tbNMI] for the FKtbNMINSRDtbNMI 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)

    Message shown after Registering Live Database stage of refreshing display.

    Failed to update:

    oEc.#8Jf: Failed to locate the target table [dbo].[tbNMI] for the FKtbNMINSRDtbNMI foreign key. ---> RedGate.SQLCompare.Engine.SqlCompareException: Failed to locate the target table [dbo].[tbNMI] for the FKtbNMINSRDtbNMI 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

    … more
    2 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…)
    completed  ·  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

12. Create Database from source control using the command line

    It would be great if it would be possible to create a database from source control using the command line interface (or some api).

    2 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…)
    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

13. Integration with SQL Refactor/SQL Prompt's "Smart Rename"

    Integration with SQL Refactor is crucial. Smart Rename should be noted by SQL Source Control and a commit should do a rename on the object in SVN to keep commit comments.

    2 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  ·  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 renaming a table 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

14. Problem with expiration

    This release of Red Gate SQL Source control...has expired. I tried to download a newer version but I am getting the same message.

    Please help me out...I would like to test your product.

    2 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

    If you need a trial extension, please contact sales@red-gate.com.

15. What's the license cost going to be?

    Can you let us know, in the general ballpark, what a normal user license will cost?

    2 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

    SQL Source Control is included in both the SQL Toolbelt and SQL Developer Bundle.

    SQL Source Control is also available to purchase separately.

    There are multi-user discounts available.

    SQL Source Control will be licensed per user.

    Please see our website for more information:
    SQL Toolbelt – http://www.red-gate.com/products/sql_professional_toolbelt
    SQL Developer Bundle – http://www.red-gate.com/products/sql_bundles/sql_developer_bundle.htm
    SQL Source Control – http://www.red-gate.com/products/sql_source_control

    If you have any questions about your current licenses or would like a quote on the bundles mentioned above, please see our website or contact Sales@red-gate.com.

16. Import sql compare project from repository by linking to repository

    Hello,

    we use SQL Compare and Subversion. We have already checked in a SQL Compare Script Folder. It would be great if you can use that Script Folder for link a database. In the actual Version there comes the error message that a project file for SQL Source Control is missing.

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

    If you were using SQL Compare to script objects to a folder and then souce controlling that, then you can link SQL Source Control to this repository and keep all your history. Information is at https://documentation.red-gate.com/display/SOC33/Using+SQL+Compare+or+SQL+Changeset+scripts+with+SQL+Source+Control. Please contact support@red-gate.com if you have any problems.

17. Support "Require BugID For Checkins" option for Vault

    In SourceGear Vault there is a repository setting that forces the user to enter a BugID when checking in changes "Require BugID for Checkins".

    SQL Source Control doesn't seem to honor this setting. It doesn't prompt you for a BugID, nor does it stop you from committing changes despite not having a BugID.

    We rely on that feature, and would really like to see it incorporated into SQL Source Control.

    2 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  ·  Gyorgy Pocsi responded

    Please download the new 2.0.3 Early Access to get the latest Vault supporting version with static data and shared model support!

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

18. show history for dropped objects

    I dropped a sp and I would like to know in which version I dropped it (I'm entering our version number in the comments)

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

    History is shown for dropped objects. Right click on the database or the object’s folder (e.g., Tables) and select show history. You will see dropped objects in the list.

19. Ability to link a change to defect in TFS

    Provide a way to link a change during commit to defect in TFS and show it in the history window

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

    You can currently use #A to associate the commit with a work item or #R to resolve the work item. If you want more than this, please see https://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/538567-add-ability-to-associate-check-ins-with-work-items.

20. Allow users to suppress the commit dependencies warning screen and automatically do not commit the dependencies.

    We don't have our schemas in source control so every time we commit code the dependencies screen comes up warning us that the schemas are not in source control. Every time we commit we have to uncheck the box and hit continue. You should allow users to suppress the commit dependencies warning screen and automatically do not commit the dependencies.

    2 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  ·  James Billings responded

    The latest frequent-update version of SQL Source Control (4.0.6.179) allows you to default the checkbox behaviour to off. To do this, you’ll need to edit your UI Options file (RedGate_SQLSourceControl_CommonUI_UIOptions.xml) which you’ll find in localappdata\Red Gate\SQL Source Control 4 and add a tag called IncludeDependenciesCheckbox, like this:

    False

    If the value is false, then the checkbox will be un-set by default.