|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Friday, April 05, 2013 9:32 AM
Points: 42,
Visits: 170
|
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Tuesday, March 08, 2011 2:22 AM
Points: 12,
Visits: 67
|
|
| is renaming an object (sp_rename) also audited ?
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Friday, April 05, 2013 9:32 AM
Points: 42,
Visits: 170
|
|
|
|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Thursday, May 16, 2013 9:21 AM
Points: 964,
Visits: 632
|
|
| This is genius!! Testing it out now. Thanks!
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Friday, April 05, 2013 9:32 AM
Points: 42,
Visits: 170
|
|
You may need some additional permissions/config if your server does not already have them:
exec sp_configure ‘show advanced options’, 1 exec sp_configure ‘Agent XPs’, 1
For reasons unknown you may also need to add exec permissions explicitly to server_audit user in the master database for:
xp_sqlagent_is_starting xp_sqlagent_notify
Both of these xp are called by sp_start_job and server_audit should have implicit exec permission via membership of msdb SQLAgentOperatorRole and cross db ownership chaining (always on for msdb and master). In general I have not needed to add these permissions but on some SQL2005 servers (so far) I have needed to. Seems strange because as far as I can see the DDL code is the same and so are the permissions.
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Tuesday, December 11, 2012 9:31 AM
Points: 5,
Visits: 77
|
|
Where are these scripts !?
install_ddl_auditing.sql and uninstall_ddl_auditing.sql
I unzipped the 2008 files - and seem to be missing major components !??
thanks
|
|
|
|
|
SSCoach
         
Group: General Forum Members
Last Login: Today @ 6:30 PM
Points: 18,733,
Visits: 12,330
|
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Wednesday, September 19, 2012 5:02 PM
Points: 2,
Visits: 49
|
|
I tried this out, and fell over at the second step, given I did not have a dbadata database already existing in my environment. I could run the 'install' script but not the 'enable' script on SQL 2005.
Once I manually created the dbadata database, and reran the 'install' script I could continue all OK!
Is this requirement for the dbadata database to already exist an omission, or an is it an assumption that you would manually create the dbadata database first?
If it's an omission, then can I please recommend it is added to the doc, as this is an extremely useful post that saved me and my colleague a lot of time and wasted energy. 
Regards, Jonathan
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Friday, April 05, 2013 9:32 AM
Points: 42,
Visits: 170
|
|
| It already explains in the article that dbadata database needs to exist in advance. Alternatively you can globally replace dbadata with another "dba database" you already have on the server.
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Friday, April 05, 2013 9:32 AM
Points: 42,
Visits: 170
|
|
| Sorry Sam but you are mistaken. All the scripts are in the zip file and always were.
|
|
|
|