Hello My Expert DBA,

Monday morning, I was in my cube, enjoying my morning tea and reviewing my daily email. As a DBA, you are aware of our daily responsibilities. LoL...Suddenly, one of our esteemed application owners knocked on my cubicle and whispered, "Zahid, my applicaiton is down!!!!!" I am familiar with his application database, which is the Orion Monitoring tool, and yes, it is a pretty large database with a size close 2 TB! I got into the box and ran sp_readerrorlog to check if there were any good insights. "The Server was rebooted," I discovered. Then I looked through the event log to check why Windows had rebooted, and I saw that there had been a windows update run over the weekend, which I interestingly looked into.

The app's owner is aware of the upgrade. However, the DBA team was not advised of this upgrade. Because SCCM Administrator applies all update or patch/CU updates. Sometimes it matters, for example, if it is production, then apply those exact updates to Test Box before applying to Prod Box. It is also critical for all of us to be aware of any updates. Because this is a huge database, I would propose notifying the DBA team first so that the DBA can properly terminate SQL Server Service to prevent data/log file corruption.

Let me talk about what happened on my database server...

Remember that if your database is in Recovery mode, you can't do anything.

Continue.........