Who made that change? It is one of those questions that can send chills down the spine of those responsible for databases. In this episode, Josephine Bush talks with us about how we can use a combination of the native tools—auditing and extended events along with some custom reporting to be prepared for questions about change when more environments are subject to regulation.
What is great about the community is their willingness to share and Josephine comes through with a set of her own scripts. What I think is most helpful is the filtering included so you only need to capture the most pertinent changes. This helps you feel confident you capture the most important pieces without all the extra logging you have to muck through when you actually have a question to answer.

Our Guest
Josephine Bush
Josephine Bush has over 10 years of experience as a Database Administrator. Her experience is extensive and broad-based, including in financial, business, and energy data sectors using SQL Server, MySQL, Oracle, and PostgreSQL along with Azure and AWS. She is a Microsoft Certified Solutions Expert: Data Management and Analytics. She holds a BS in Information Technology, an MBA in IT Management, and an MS in Data Analytics. She presents at SQL conferences and user groups around the world. She is the leader of the Boulder SQL user group. She blogs on sqlkitty.com and you can reach her on Twitter @hellosqlkitty.
Never Miss An Episode
Subscribe to get podcast notifications by email.
“There is not just SQL Server Audit. You can use Extended Events to also audit, and I use that in a lot of cases, especially on older servers.”
Josephine Bush
3 Takeaways
- Auditing can help you get in front of the dreaded question—who made that change?
- Scripts from the community can make this process more approachable.
- Creating the audit is only the first piece—a reporting option should also be part of your plan.
Leave a Reply
You must belogged in to post a comment.