1 DBA's Professional Blog
Legislation and regulation sometimes dictates that certain activities must be tracked within a database. On occasion, it will be required that queries be audited and tracked to reach compliance with the legislation or regulation. To achieve this compliance, this article will demonstrate how to use Extended Events to audit statements being executed within the database.
We live in a day and age when security (data, network, server, etc) is seemingly at the forefront of the daily news.
This month I am asking you to not only write a post but to do a little homework – first. In other words, plan to do something, carry out that plan, and then write about the experience.
Parsing XML is the epitome of salt in a wound for a DBA. Parsing the XML from Extended Events need not be so painful. Read further to discover how to remove the pain from the task of XML parsing.
This month I am asking you to not only write a post but to do a little homework – first. In other words, plan to do something, carry out that plan, and then write about the experience.
Finding the right event or combination of events to monitor may seem like quite a daunting task with so many events to explore and (frequently) too little familiarity with Extended Events.
When working with Extended Events, there are times when a little more information is, well, helpful. You know you want to use extended events to try and monitor for a specific thing to happen.
SQL Agent job schedules should be easy to read for humans if for nothing else than the fact that you have to provide this information to the auditors from time to time.
Working diligently as any good DBA might, you have established maintenance routines for each of the SQL Servers under your purview. Then a small problem occurs: Index Cannot Be Reorganized…
Three days of presentations in Richmond Virginia. From Naked SQL to Wheel of Doom – there is a wide breadth of knowledge to be shared.