May 18, 2010 at 2:16 pm
My boss found a table in live data that we can't account for on who created it or what it's for. Barring a security issue & whatever along those lines I'm creating a trigger to fire off if someone alters/drops/creates a table in a database.
As you probably already know I can do this at a database level with no problems. Is there a way to put a trigger at the server level to trip the ALTER_TABLE/DROP_TABLE/CREATE_TABLE when anything is done at the database level? Or will I be stuck putting this trigger on each database?
Thanks!
I know, I know...my subject line is back-a$$-wards. Should be "Database trigger at server level" :Whistling:
May 18, 2010 at 2:21 pm
My guess is you should have them on each of the databases in that Server
These should help you..
http://www.sql-server-performance.com/articles/audit/ddl_triggers_p1.aspx
http://www.developer.com/db/article.php/3552096/Using-DDL-Triggers-to-Manage-SQL-Server-2005.htm
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
May 18, 2010 at 2:23 pm
Bru Medishetty (5/18/2010)
These should help you..http://www.sql-server-performance.com/articles/audit/ddl_triggers_p1.aspx
Coincidentally I've been using that one all day working on my issue. 😀
Bru Medishetty (5/18/2010)
http://www.developer.com/db/article.php/3552096/Using-DDL-Triggers-to-Manage-SQL-Server-2005.htm
Found this one as well. Still reading it.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply