This month marks the 45th month in Adam Machanic’s (b|t) T-SQL Tuesday blog party which started in December of 2009. Each month an invitation is sent out on the first Tuesday of the month inviting bloggers to participate in a common topic. On the second Tuesday of the month all the bloggers post their contribution to the event for everyone to read. The host sums up all the participant’s entries at the end of the week. This month I’m the host and the topic is …
An audit trail is needed for various reasons. Some companies need it for compliance, others need it to find out who “accidently” did something stupid last week, and some specialized audit trails can tell you how the data has changed over time.
So, it is time to follow Dorothy and Toto down the yellow brick road and to share your experience with auditing data. If you are new to the T-SQL Tuesday blog party and need some ideas, here are a few:
- How to implement SQL Server Audit which was introduced in SQL 2008.
- Your favorite audit pattern.
- Your worst experience with an implementation of a bad auditing pattern.
Pay no attention to that man behind the curtain!
The Great and Powerful Oz has spoken! … and these are the rules.
Rule 1: Make sure that you include the T-SQL Tuesday image at the top of the post which will help identify your post as a T-SQL Tuesday blog post. Please include a link back to this invitation too.
Rule 2: Sometime next Tuesday using GMT, here’s a link to a GMT time convertor, publish your blog post. For example in California, that would cover 5 pm Monday to 5 pm (PDT) Tuesday.
Rule 3: Come back here and post a link in the comments so that I can find all the posts for the round up.
Rule 4: Don’t get yourself fired. Make sure that you either generalize your post or get permission to blog about anything from work.
Rule 5: If you roam the Twitterverse, then don’t forget to Tweet about your blog post with the hashtag #tsql2sday.
Rule 6: Go read someone else’s blog on the subject!
Final Rule: Have fun!