SQL RNNR

Extended Events is a powerful tool with plenty of ease of use and flexibility. This flexibility allows the DBA to capably monitor the server for any issue be it small or large. This article demonstrated how to use Extended Events to monitor for a specific wait_type and the same principles can be applied to any of the waits you may need to investigate.

Not only should you pay respect to those giving of their time, but you should spend a little time to also give back to the community. I will say it again, the more you give of yourself to help others learn your trade, the more you will personally learn and grow in your professional and personal self. It is an investment well worth taking.

Extended Events is a powerful tool with plenty of ease of use and flexibility. This flexibility allows the DBA to better service the needs of the developers when the developers need access to the trace data.

Seldom does a DBA have the opportunity to get out in front of infrequent or random errors such as implicit conversions. More often than not, it is the privilege of the DBA to find out about the problem after the fact from a developer or, worse yet, an end-user.

Implicit conversions are not uncommon in the computing world and can be viewed as kind of a fail-safe for when we don’t quite follow decent practices when designing the database or when writing queries or both.

Migrating Extended Event Sessions from one server to another should be a simple task. So simple, one would think there was no need to give it a second thought, right?

How does one consistently find the correct path to the Extended Event Log file (XEL file)? This article shows a thorough method to capture that information for all sessions on the server.

One of my favorite database automations is to send trivia style questions daily. This helps me to mentor and assess other dba talent within an organization without being too aggressive. Not only can a database be used for automation but it can also be used for numerous other automations. Beyond being highly useful for automation and training, there is also the possibility of using TSQL to solve puzzles like Sudoku puzzles.

A database can be offline at the time that you take over responsibility of the database. You will be asked when it was taken offline. This script will help you get a reasonable deduction for that offline event in the absence of better data.

Database recovery (crash recovery) is a nerve wrenching situation under the wrong conditions. It can be as bad as a root canal and just as necessary to endure that pain at times. When the business is waiting on you waiting on the server to finish crash recovery, you feel nervous at best. If you can be of some use and provide some information back to the business, that anxiety dissipates and the business becomes more calm as well. While the previous script can help you get that information easily enough, I want to introduce the easiest method to capture that information currently available.

Thanks Solomon. This was a long time ago, but I believe the specific requirements were to sort those characters in…

Hi Jason. I realize that it's been 7 years since you posted this, but do you remember the details enough…

Thanks Solomon for that thorough article.

Adam, this approach will actually change user databases (not just the database's default collation, but also the collation of the…

Hi AG. As far as Instance-level collation goes, that also controls variable names, cursor names, and GOTO labels. Also, technically…

Glad it wasn't just me... ^_^ GRR ARRGGGHHHHH!

Jason, great post and work in explaining the XE. I was hoping if you can create an article or one…

A bigger problem I've seen than connecting through a dialog box like Management Studio does, is when developers or testers…

Actually that is more of an "it depends" rather than the rule. Read these debunked myths which I am sure…

90% is not a good idea if the tables primary key is an identity as data then is always going…