Skip to content
← SQL Source Control

How can we improve SQL Source Control?

SQL Source Control

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Evaluate TFS Policies (Rules) when Committing DB Changes

We need SQL Source Control to comply with the policies in force for the project. eg. Checkin policies, associate with workitem policy.

57 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
AdminRedgate Administrator (Admin, Redgate) shared this idea  ·   ·  Report…  ·  Admin →
completed  ·  AdminStephanie (Product Manager, Redgate) responded  · 

SQL Source Control 3.3 now evaluates TFS policies when committing DB changes. For more information see http://documentation.red-gate.com/display/SOC3/This+commit+doesn%27t+meet+the+server%27s+policy+requirements%2C+or+the+policy+isn%27t+configured+on+your+machine.

To upgrade, use SQL Source Control’s “Help > Check for Updates…” menu item, or download directly from http://www.red-gate.com/dynamic/products/sql-development/sql-source-control/download.

Show previous admin responses (3)

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • AdminDavid Atkinson (Product Manager, Redgate) commented  ·   ·  Report

    Yes, better work item support is also something we'd like to look at for v4. If it's a showstopper for you, you could always consider using SQL Connect (our Visual Studio add-in) to commit your database changes. As this is in VS, it benefits from all the policies enforced by VS.

  • philcart commented  ·   ·  Report

    David, basic policies we use are "Changeset comments" and "associate with work item". It'd be really, really useful to not have to use the #A & #R hacks to associate workitems too. So sort of GUI element has been promised for way too long.

  • AdminDavid Atkinson (Product Manager, Redgate) commented  ·   ·  Report

    Unlike most source control systems TFS doesn't enforce this at server-side, which means that clients (such as SQL Source Control) have to explicitly implement support for the policies and implement the enforcement. We have tentatively penned this for the SQL Source Control v4 release, which won't be released till next year. What is the most important policy that you need to enforce?

  • Ken V. commented  ·   ·  Report

    Uhm, yes. We just started using Check-IN Policies (Sorry my developers, the wild wild west is over). I was SHOCKED! to see that SQL Source didn't support Check-In Policies. Actually, I am more Shocked that TFS even allows a check-in with out the policies. So, yes, I think this is a must.

    Right up there with adding support for Shelve Sets!

  • Riccardo commented  ·   ·  Report

    I agree, great product (we are using the developer bundle) but evaluation of policies is definitely missing + selecting from list of assigned workitems prior to the checkin. (the comments textbox alone is not good enough)

  • Alan commented  ·   ·  Report

    I'm slightly disappointed that the source control software can't do this. Everything else works so well. Our department would really love to have this feature just to make sure people don't forget.

  • Marty U. commented  ·   ·  Report

    We are currently evaluating Red-Gate again due to the terrible performance and overhead with managing multiple large databases in Visual Studio Database Projects. We have these same rules that would need to be enforced before we could move our 20 developers over to this product I believe. Our Audit department would not be happy about this not occurring.

  • Zach commented  ·   ·  Report

    I understand there is a way to associate a workitem with a check-in and this is great but I need my TFS rules to be enforced by a SSC check-in. Currently if I do not associate a check-in with a workitem it will check-in anyways even though I have a rule that states all check-ins must be associated with a workitem.