53 results found

1. Add filter option for filegroups

   Add an option in the SSC filter to ignore differences in filegroup location as there might be multiple instances of a controlled database that have different filegroup configurations

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

2. Add Filter to Migration Scripts

   Add Filter to Migration Scripts

   When you go to create the migration script, you get to choose which commits are part of that script. It would be great to sort the migration script by the product descriptions or tags. When we have multiple commits to a database, and we might commit #project1 and #project 2 back and forth for a month, and instead of having to ctrl click through every other one, it would be great if we could group them together (or filter) and then generate the migration script easier.

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

3. Customize headers, footers and batch footers in migration script

   I'm hard pressed to think of any corporation that would take a migration script and run "as is". You will at the minimum have some standard code or comment block to put at the top and bottom of a script.

   For example, in our particular place, we check the DB version before running a script (header), and stamp a version on success / error handle (footer).

   We also have special statement which we need to put after each batch (where the migration currently places a "GO").

   Needless to say, having to manually do this is time consuming. So my suggestion is the ability to customize what goes at the top, bottom and after each batch (GO) on the migration scripts. This would be a huge time saver.

   If you are already allowing this, great (I am unable to join your beta as I'm in an agile dev team).

   I'm hard pressed to think of any corporation that would take a migration script and run "as is". You will at the minimum have some standard code or comment block to put at the top and bottom of a script.

   For example, in our particular place, we check the DB version before running a script (header), and stamp a version on success / error handle (footer).

   We also have special statement which we need to put after each batch (where the migration currently places a "GO").

   Needless to say, having to manually do this is time consuming. So my suggestion… 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…)
   0 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

4. When committing, show when multiple people have edited an object

   When comitting:
   Andy makes an edit and "Changed By" shows "Andy" (but does not yet commit).
   James then makes an edit and "Changed By" is now "James", but does not mention "Andy"

   It would be useful if it could show "Andy, James", to highlight a potential conflict.

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

5. prevent timeout on commit changes tab for larger db in shared database model

   prevent timeout on commit changes tab for larger db in shared database model

   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  ·  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
   under review  ·  Paul Stephenson responded

   The timeout occurs when SQL Source Control runs a SQL query to find out which user made the changes that need to be committed, and the server takes too long to respond.

   SQL Source Control 3.6.0 improves this situation, so that if a timeout occurs you can still go ahead with the commit. This version is currently available on Frequent Updates. To learn how to turn on frequent updates, see: http://www.red-gate.com/products/sql-development/sql-source-control/frequent-updates

6. Detail the SQL roles required for SQL Source Control needs to commit code

   Provide details

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

7. Create a 'Mixed' model in addition to 'Shared' and 'Dedicated'

   We generally share one database, but occasionally our developers keep a local version. All of these point to source control, which we consider the 'official' version of the database. A developer could commit changes to source control from their dedicated database. They could even edit the code manually.

   However, if we set up the shared database under the 'shared' model, we can't get latest from source control.

   We currently work around it by setting every database as 'dedicated', even the shared database, but then we miss out on keeping track of which users made which modifications.

   Please offer a 'Mixed' database model or enable 'Get Latest' on shared databases.

   We generally share one database, but occasionally our developers keep a local version. All of these point to source control, which we consider the 'official' version of the database. A developer could commit changes to source control from their dedicated database. They could even edit the code manually.

   However, if we set up the shared database under the 'shared' model, we can't get latest from source control.

   We currently work around it by setting every database as 'dedicated', even the shared database, but then we miss out on keeping track of which users made which modifications.

   Please offer a 'Mixed'… more

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

8. BUG: Sql Source control doesn't maintain WITH (IGNORE_DUP_KEY=ON) on table type

   I have a table type with "(IGNOREDUPKEY=ON)" on it. Sql Source control doesn't preserve this and doesn't see this in the SqlServer database schema on the table type

   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  ·  Better Support for Shared Db Dev Model  ·  Edit…  ·  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

9. Prevent false commit

   If I make a change to a proc in management studio editor, then execute the alter. That change is not reflected in object explorer until i do a refresh of object explorer. After the commit SQL source control still show a change and this can result in your change reverting if you press commit again. Therefore sql source control should do a refresh of the committed object in object explorer after every 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…)
   0 comments  ·  Better Support for Shared Db Dev Model  ·  Edit…  ·  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

10. I am allowed to commit previous changes that upon refresh would show newer changes. Can there be a check for this on commit?

    I want a check on commit for all the items I intend to check in to make sure that there is not a newer version available. In the case where there is, I want to be presented with a list of those changes for review before anything is committed.

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

11. On conflict when commiting changes able to right click and open proc/table in new sql editor

    When you get conflict when commiting changes it would be nice to be able to right click and open proc/table in new sql editor, do you change (merge) and continue.

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

12. For shared development environment, replace "GET ALL" with list of historical changes made

    When developing in shared enviroment, I'd love a history tab that I can review all revisions with details, and not have to have a modal window separately. I believe this should be integrated into the main source control tab as change history log. This could help make others aware of changes made that could affect them, yet were already committed. Thanks!

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

13. Cannot Get Latest

    Everytime I try to Get Latest I get the following....

    System.Exception: Failed to update to the head revision after 10 attempts ---> System.Exception: Failed to update to the head revision after 10 attempts
    at RedGate.SQLSourceControl.Engine.LinkedDatabase.GetDatabaseFolderWorkspaces(ICancellableOperationStatus status, IScriptFolderStructure scriptFolderStructure, IReadOnlySourceControlServerCallBacks callBacks, SourceControlRevision& revision)
    at #GWeb.#WXM.#Fieb()
    at #GWeb.#Wheb.#tieb(Func1 )
at #GWeb.#WXM.#8ZW(Boolean )
at #GWeb.#XXM.#yRW()
at #GWeb.#WXM.#qYM()
at #GWeb.#XXM.#iS()
at #qlhb.#0heb.#l36(String , #1heb , ICancellableOperationStatus )
at #qlhb.#K3c.#83c(String , #O9U , ICancellableOperationStatus , IReadOnlySourceControlServerCallBacks )
at RedGate.SQLSourceControl.Engine.Diff.Memoization.ReattachableMemoizer.#A3.#eL5b(ICancellableOperationStatus )
at RedGate.SQLSourceControl.Engine.Diff.Memoization.ReattachableMemoizer.#YZBc.#jzb.#Qnw()
--- End of inner exception stack trace ---
at RedGate.SQLSourceControl.Engine.Diff.Memoization.ReattachableMemoizer.#YZBc.#VAb.#xSXc()
at RedGate.SQLSourceControl.Engine.Diff.Memoization.ReattachableMemoizer.#uz2b(String , IDatabaseConnection , #1heb , ICancellableOperationStatus , IReadOnlySourceControlServerCallBacks , Action )
at #qlhb.#0heb.#wieb(IBoundDatabase , ICompareOptions , Boolean , ICancellableOperationStatus , IReadOnlySourceControlServerCallBacks , Action )
at #GWeb.#VXM.#mYM[#NrPb](IBoundDatabase , Func2 , ICancellableOperationStatus , IReadOnlySourceControlServerCallBacks , IDifferenceSelector , Action )
    at #GWeb.#VXM.#kYM(IBoundDatabase , ICancellableOperationStatus , IReadOnlySourceControlServerCallBacks , IDifferenceSelector )
    at #GWeb.#4Ec.#8Jc(ICancellableOperationStatus , IReadOnlySourceControlServerCallBacks , IDifferenceSelector )
    at #GWeb.#4Ec.#izb.#SB7b(ICancellableOperationStatus )
    at RedGate.SQLSourceControl.Engine.Cancellables.MutexedCancellableOperation1.#u3.#k5f()
at RedGate.SQLSourceControl.Engine.Cancellables.CancellableOperationBase.InvokeWithTracker(String featureUsageKey, Action action)
at RedGate.SQLSourceControl.Engine.Cancellables.MutexedCancellableOperation1.Invoke()
    at #eEc.#Qlg.Invoke()
    at #JLc.#PLc.#Jfb.#EJf()
    at RedGate.SQLSourceControl.Engine.SmartAssembly.ExceptionReporting.ErrorReporterBase.Do(Action , Predicate1 , Boolean )
at RedGate.SQLSourceControl.Engine.SmartAssembly.ExceptionReporting.ErrorReporterBase.DoWithObviousExceptionsRethrowAll(Action action)
at RedGate.SQLSourceControl.CommonUI.Forms.ErrorDialog.DoWithObviousExceptionsRethrowAll(Action action)
at #JLc.#PLc.#CTc(ICancellableOperation1 , Object )

    Everytime I try to Get Latest I get the following....

    System.Exception: Failed to update to the head revision after 10 attempts ---> System.Exception: Failed to update to the head revision after 10 attempts
    at RedGate.SQLSourceControl.Engine.LinkedDatabase.GetDatabaseFolderWorkspaces(ICancellableOperationStatus status, IScriptFolderStructure scriptFolderStructure, IReadOnlySourceControlServerCallBacks callBacks, SourceControlRevision& revision)
    at #GWeb.#WXM.#Fieb()
    at #GWeb.#Wheb.#tieb(Func1 )
at #GWeb.#WXM.#8ZW(Boolean )
at #GWeb.#XXM.#yRW()
at #GWeb.#WXM.#qYM()
at #GWeb.#XXM.#iS()
at #qlhb.#0heb.#l36(String , #1heb , ICancellableOperationStatus )
at #qlhb.#K3c.#83c(String , #O9U , ICancellableOperationStatus , IReadOnlySourceControlServerCallBacks )
at RedGate.SQLSourceControl.Engine.Diff.Memoization.ReattachableMemoizer.#A3.#eL5b(ICancellableOperationStatus )
at RedGate.SQLSourceControl.Engine.Diff.Memoization.ReattachableMemoizer.#YZBc.#jzb.#Qnw()
--- End of inner exception stack trace ---
at RedGate.SQLSourceControl.Engine.Diff.Memoization.ReattachableMemoizer.#YZBc.#VAb.#xSXc()
at RedGate.SQLSourceControl.Engine.Diff.Memoization.ReattachableMemoizer.#uz2b(String , IDatabaseConnection , #1heb , ICancellableOperationStatus , IReadOnlySourceControlServerCallBacks , Action… 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  ·  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

14. On shared mode, Source control sync delayed issue

    Shared mode is perfect for small team DEV environment, but status update delayed to sync is annoying....is there a way to config the sync frequency?

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

15. Provide a way to post configurations that must be implemented as TO DO items

    I have a service broker application where some parts such as service routes etc must be defined per database configuration, thus certain components change per installation so it would be nice to tag such items as TO DO items, like wise once complete when comparing to latest or changes the item is not displayed as an object that has changed.

    Going further it might be nice to populate table data that also configures per installation as well

    perhaps use of extended properties, or a file present in source. I had taken the source code and placed a comment in it hoping it might at least show up during sql compare or getting latest code, didn't work on database level objects

    I have a service broker application where some parts such as service routes etc must be defined per database configuration, thus certain components change per installation so it would be nice to tag such items as TO DO items, like wise once complete when comparing to latest or changes the item is not displayed as an object that has changed.

    Going further it might be nice to populate table data that also configures per installation as well

    perhaps use of extended properties, or a file present in source. I had taken the source code and placed a comment in it… 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  ·  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

16. compare what I am about to check in against the previous check in

    I see the changes to be checked in , these may have been done by other developers. I want to compare the changes about to be checked in against the previous version to see what changed before I check in.

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

17. Still having to manually apply indexes to tempdb to prevent timeouts

    I had to apply this index to tempdb (created by my missing index script).

    CREATE INDEX [missingindex2019RG_AllObjects] ON [tempdb].[dbo].[RG_AllObjects] ([Expired]) INCLUDE ([DatabaseID], [ObjectType], [ObjectID])

    This is a work-around until the DB service gets re-started and then I have to re-execute the statement because tempdb gets re-built.

    Also, there is no way that I know of to disable Sql Prompt which was blocking the create index statement. The only way I got the index applied was to hop to another computer without Sql Prompt.

    Index management in tempdb needs to be managed better.

    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  ·  Better Support for Shared Db Dev Model  ·  Edit…  ·  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

18. Link source control to Schema, not database

    We couple applications with schemas, not databases. It would be great to link source control to just one schema, rather than the entire database. This way, we can source the code for the application and the database in the same branch

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

19. Move Column Order

    the ability to move column order
    Example I would like the Owner Column next to the Object Name

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

20. SQL Source Control support SQL Server maintenance jobs

    It would be mint* to be able to have SQL Server Maintenance jobs included in SQL Source Control. Could it be added as a new feature?

    • (see kid from Super8 movie)
    29 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