March 25, 2009 at 2:07 pm
Apparently someone adjusted the settings on one of our server's maintenance plans.
Instead of being set for X days until it removes backups, it was X-5 days.
So backups are not staying in the backup folder as long as they should.
Not a big deal, but I was wondering if there is any way to audit who changed the plan, all I can see tracked is the plan's creation date and owner, I'm guessing that SQL Server 05 does NOT track data on who modified the plans, but thought I would ask.
Thanks!
March 25, 2009 at 2:26 pm
I doubt it. If it's not a busy server the default trace might have something in there.
I don't see versioning like there was for DTS packages.
March 25, 2009 at 5:42 pm
Maxer (3/25/2009)
Apparently someone adjusted the settings on one of our server's maintenance plans.Instead of being set for X days until it removes backups, it was X-5 days.
So backups are not staying in the backup folder as long as they should.
Not a big deal, but I was wondering if there is any way to audit who changed the plan, all I can see tracked is the plan's creation date and owner, I'm guessing that SQL Server 05 does NOT track data on who modified the plans, but thought I would ask.
Thanks!
Check out Default Trace if you don't have idea about it. Enable the Default trace and create a table on your server and dump the data into this table. you can query the table you created whenever needed and also maintain a job to clean up this table. That's the best way to go
March 26, 2009 at 6:53 am
I thought the default trace was enabled by default on MSSQL 05?
Additionally I thought that server side traces could only dump their data to log files, only profiler lets you select a database table to dump trace results to.
So for a server side trace wouldn't you have to dump to a log, then find some way to pull data out of that log on a regular basis and dump it into a table?
Am I perhaps mistaken in that understanding?
I would VERY MUCH like to dump log data to a table, as I could then build a nice set of SSRS reports to let me more easily view and analyze the trace logs.
March 26, 2009 at 10:01 am
Yes, it is enabled by default, the best way is to create a job to dump the data from the trace.
Check this one out:
http://www.sqlservercentral.com/articles/SQL+Server+2005/64547/
and this one:
March 26, 2009 at 1:45 pm
I appreciate the links, thanks!
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply