This is the summary of blog posts for T-SQL Tuesday #45 – Follow the yellow Brick Road. I was the lovely host this month with the topic being Auditing. As always, I enjoyed all the posts. It reminds of what Forest Gump once said:
“It’s like a box of chocolates. You never know what you’re going to get.”
So, let’s meet up with Dorothy to find out what kind of auditing related advice and stories she found on her journey.
Jason Brimhall had a wonderful post about using the information that SQL Server automatically gathers for us. He used the sys.FN_TRACE_GETINFO function to find out when and who executed the DBCC SHRINKFILE command in his environment.
Rob Farley wrote a thought-provoking post about how you should think about your auditing data you do have and how you shouldn’t make excuses when you don’t have it.
Boris Hristov wrote a piece about the impact of external auditing entities on our activities. In this case, it was a story about unintentionally scaring the client about database security levels and how that could have impacted a SOX audit. Side note: I always enjoy Boris’ enthusiasm about T-SQL Tuesday. (keep it up Boris. )
Chris Yates wrote a great summary piece about what to audit and a list of various tools to use to accomplish the auditing.
Steve jones wrote a wonderful piece on why auditing is important and how he caught a “cowboy coder”.
Steven Ormrod wrote an excellent piece on how to use a DDL Trigger to not only find out who modified the database, but from what IP address and application they did the deed. This is definitely one to bookmark.
Glenda Gable shares with us how she learned about writing triggers that audit. She then goes on to share with us how she had an opportunity (and seized it) to learn and implement Change Data Capture (CDC).
Jeffrey Verheul wrote about taking the initiative at a new company and creating a baseline on the system health of the 70 databases he was responsible for… and it paid off in a relatively short amount of time.
Dave Green wrote a thought-provoking post about what to do with the audit data during a data migration. I particularly enjoyed this post, since I get to ask my clients those very same questions next week. (Can we say perfect timing?)
Robert L Davis wrote about a type of auditing that I hadn’t even considered, and I’m happy he did. He wrote about a new feature in SQL Server 2012. SQL Server 2012 will automatically audit the execution of your SSIS package. He goes on to share how he was able to use the feature.
Mickey Stuewe (that would be me), wrote about a simple way to audit at the data level. She also made a plea at the end of her post to all the women bloggers out there. She asked them to contact Adam Machanic (b|t) about being a T-SQL Tuesday blog party host.
…And That’s A Wrap
Thank you to the 11 bloggers who participated this month. We couldn’t have T-SQL Tuesday without you. Thanks also to Adam Machanic who put this brilliant idea in action and makes sure it continues each month. … Only 14 more days until the next invitation goes out.
[…] T-SQL Tuesday #45 – Follow the Yellow Brick Road (summary) […]
[…] Boris Hristov wrote a piece about the impact of external auditing entities on our activities. In this case, it was a story about unintentionally scaring the client about database security levels and how that could have impacted a … […]
Thanks so much for hosting this month’s T-SQL Tuesday. I’ve enjoyed reading your blog over the past few months.
Thanks Steven. I’ve enjoyed yours as well. It’s one of my favorite perks of T-SQL Tuesday: being introduced to new (to me) bloggers. 🙂