1 DBA's Professional Blog
What is this gaping hole in the coverage of Extended Events? To be honest, it is not a very complicated topic or very difficult gap to fill. It’s just something that has been overlooked. The gap boils down to this: how does one consistently find the correct path to the Extended Event Log file (XEL file)?
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.
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.
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 Server 2016 has come with a ton of cool features, bells, whistles and well cool stuff (yes redundant). That aside, what are some of the really cool features that I would love to see in SQL Server?
There are a lot of cool features in SQL Server that ROCK! It is really hard to pick just one with so many cool features that can make life much easier as a DBA.
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.
The use of SQL Audit can be viable to track the changes that may be occurring within your SQL Server – from a settings point of view