1 DBA's Professional Blog
It is quite common to be required to investigate performance issues on the server. With this, it is occasionally necessary to be able to interpret an obfuscated job name. Learn how to do that in this article.
In this article, we will explore database backups. More specifically, how do you truly know if you have a successful backup? Here’s a hint: it has to deal with restores.
In this article I explore the basic of querying backup history data as a foundation to reporting on essentials such as storage and job management.
In this article I explore the basics around how to determine when a database was last restored.
Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
Do you know that your Server logs 300 million deprecation events a week? Do you know if code needs to be updated or how to find deprecated uses in SQL Server?
What do you do when a developer comes to you and asks, “Where did the database go? The database was there one minute, and the next it was not.”
With the evolution of SQL Server, there is an evolution in Extended Events. New features in SQL Server also means there may be some additional default sessions.
Within the world of SQL Server there are a few things one can be certain of – things will change. This is true of the features in SQL Server. Additionally, Extended Events is constantly evolving which underscores this constant change.
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)?