Knowing your SQL Server

I have only been a DBA (database administrator) for little over a year. One thing Brent Ozar recommends in his training’s is knowing your inventory. I didn’t realize how important it was until I started patching servers.

What I realized it is very easy to get lost in amount of information DBAs can gather, more easily if you work for a big firm and dealing with several different products, in different environments. Information overload is bad, hence I recommend having a simple system to collect data that you can track and repeat on regular basis. Remember it is not about doing it now, but how you can pull up your sleeves and get it done over and over again whenever needed and how quickly.

Here is a simple sql query that helps me get to know exactly what I need to know about each of my servers.

What am I collecting

  1. Server Name
  2. KB Version (This is optional)
  3. BuildVersion — Since not everyone know what each build version means, we need to convert it into meaningful name. This comes in handy when creating reports for upper management.
  4. ServicePack and Cumulative Update (This is good to know and audit to make sure that all your servers are on same level if need to be -unless there are exceptions)

In next article, I will share how to generate report and have count ready, to answer questions when your CTO drop by and ask you how many servers we have and what version they are on.

Originally published at



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Sanchit Wadhwa

I help solve data problems |Need help ? email me > | website > | ❤ Books, music, dance, food, podcasts, soccer, writing