SQL Clone
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in

Default Instance Reports – Configuration Changes History

Hey, who changed the max memory setting for the xyz instance? The good news is that this information is captured in the default trace. Even better is the fact that there is a report that will pull the data out of the default trace and make it nice and easy to see.

You get to see the old value as well as the new, who did it, and when. The big downside is the fact that the default trace is only so big so the more active your instance is the less time you have before the information goes away. Because of this, you might consider creating a daily job to pull the information into a logging table. You won’t be able to use the report but at least you’ll have the data.

Filed under: Auditing, Microsoft SQL Server, Settings, SQLServerPedia Syndication, SSMS Tagged: default trace, microsoft sql server, Reporting, SSMS


My name is Kenneth Fisher and I am Senior DBA for a large (multi-national) insurance company. I have been working with databases for over 20 years starting with Clarion and Foxpro. I’ve been working with SQL Server for 12 years but have only really started “studying” the subject for the last 3. I don’t have any real "specialities" but I enjoy trouble shooting and teaching. Thus far I’ve earned by MCITP Database Administrator 2008, MCTS Database Administrator 2005, and MCTS Database Developer 2008. I’m currently studying for my MCITP Database Developer 2008 and should start in on the 2012 exams next year. My blog is at www.sqlstudies.com.


Leave a comment on the original post [sqlstudies.com, opens in a new window]

Loading comments...