One of my pet-peeves (and consequently frequent topic of discussion) is finding database settings (or any setting that has changed) without knowing about it. Worse yet is finding that the change has occurred and nobody […]
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 […]
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.
We have the distinct pleasure once again to have a party full of SQL enthusiasts. The best part is that few if any of us are even in the same room or building for this […]
Do you know the last time a Server Property was changed on your instances of SQL Server? Are you wondering when the setting for max degree of parallelism was changed? Do you know who changed […]
From time to time I see a question asking how to determine the last time a SQL Server was either restarted or when the last time was that the database was used. For the first […]
Checking for BLOBs that were created in the Primary Filegroup by default. To move them was a manual process and is a different topic from the crux of this one. Since the initial report to find the BLOBs, I have evolved it somewhat to try and find the size of each object, as well as to report on the usage related with each.
A picture is worth a thousand words, right? Sometimes, a picture for an event session just may be able to say it better than 50-60 letters used to try and describe the session.
Planning to upgrade/migrate requires a fair amount of prep work. Some of that prep work involves auditing your server for any users that may still be using the instance.