Challenge on DDL Triggers and Policy Management

  • I was just told today that DDL triggers can't override an established Policy Management "thing" on a server. Now I find it a bit hard to believe that MS has covered every possibility on this given my previous experience with DDL triggers, so I'm coming to the group.

    I am offering that old standby, the "Marvel No-Prize" for anyone who can help me discover a DDL trigger that gets around the Policy Management capabilities of SQL 2k8.

    Anyway want to help me take up the challenge? @=)

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • I'll give it a try, however, since the policies are implemented as DDL triggers behind the scenes, I don't think it's possible.

    Are you talking about a policy that prohibits a certain change (like forcing all databases on a certain server to be in full recovery)?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Well, see, that's what I wasn't sure about. How the global policies in 2008 actually functioned under the hood, that is.

    I'm referring to a situation that I ran into with SQL 2k5. There is a DDL trigger which prevents users from being added to roles, but ISTR that when I tried it, there was a system stored procedure which allowed me to circumvent the DDL trigger.

    I don't remember exactly what it was (I discovered it sometime last year), but I do recall posting about it here and at MS's website. I think they may have put a note about this issue in the "Fix for 2008" category (completely ignoring the fact that we might want it fixed for 2005 as well).

    @sigh. Yet another problem with MS. They'll solve our problems, but only for the next iteration of SQL. We still have to live with the bugs on the current version. @bleargh.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • I'll give it a try, but it won't be in the next couple of days. I've got *real work* that needs doing :crying:

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Me too. Which means I can't fiddle with SQL 2008 nearly as much as I want to.

    @sob!

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • DDL triggers would have an internal hierarchy wouldn't they? kernel stuff up high, security stuff, server scope, db scope.. or something?

  • Please note: 2 year old thread.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply