In the previous article on this topic (which can be read here), I discussed the problem of having a database get dropped and the need to find out who dropped the database and when they dropped […]
Using Extended Events to trap/trace information allows the trapping of that information to various targets. One of the targets I will frequently tell people to use is the file target. The reasoning for this is the […]
Extended Events is a wonderful tool. Execution Plans are also some wonderful things – or are a wonderful tool as well. Both of these tools are fantastic for troubleshooting. Combined, they can potentially be even better. […]
I bring you yet another installment in the monthly meme called T-SQL Tuesday. This is the 67th edition, and this time we have been given the opportunity to talk about something I really enjoy – […]
In the first article on this topic (which can be read here), I discussed the problem of having a database get dropped and the need to find out who dropped the database and when they […]
If you just so happen to be running on SQL Server 2012 or later, you will need to change your event sessions that were tracking file changes. It is a bit of an exercise to make the change and can be frustrating, but it is well worth it. The improved data that can be captured is going to help better control and oversee the environment.
Really, at this point what is there that hasn’t been done about the ghosts? Well, if you are well tuned to these apparitions, you may have received the urge to explore them with Extended Events – sometimes called XE for short.
Gathering event information is a pretty good thing. It can do wonders for helping to troubleshoot. What do you do if you need or want to be able to review the captured information in 3 months or maybe 12 months from now?
Creating a custom data collector can be very handy for a DBA. Especially in times of troubleshooting. These collectors are also quite useful for trending and analysis. Consider this a tool in the chest for the poor man.