Today is another one of those installments in the long-running TSQL Party held monthly (a.k.a TSQL2SDAY). This month we have an open invitation from Mike Donnelly (blog | twitter), asking us to talk about something new […]
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 […]
In a recent article on SSG, I discussed how to use Extended Events to function in a Profiler like fashion. You can read about that here. I recommend reading that article first because it helps […]
Recently I wrote an article about Capturing Online Index Operations. In that article, I discussed a problem that I had encountered. Well, there were multiple problems. One was an issue with a vendor app that […]
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.
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?
This is the ninth installment in the 12 day series for SQL tidbits during this holiday season. Previous articles in this mini-series on quick tidbits: SQL Sat LV announcement Burning Time Reviewing Peers Broken Broker […]
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.