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?
1 DBA's Professional Blog
T-SQL Scripts
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.”
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)?
We live in a day and age when security (data, network, server, etc) is seemingly at the forefront of the daily news.
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.
SQL Agent job schedules should be easy to read for humans if for nothing else than the fact that you have to provide this information to the auditors from time to time.
Are you rolling the dice with your love/hate relationship with XML? Tune in to see how you can ease your XML frustration along with increasing your free time to do more important things.
The joys of inheriting a new database and being thrown into the fire to quickly assimilate as much information about the database as possible can be troublesome. This script will help with that!
Newest update to the script to help discover and track object sizes within a database.