Question: How to Check Status of Instant File Initialization?
Answer: This is a follow-up question of the previous blog post which I shared earlier. Please read this blog post before reading this blog for complete information: How to Check If Instant File Initialization Enabled or Not?
The question such as this makes my day during the Comprehensive Database Performance Health Check. One of the DBA asked if there is an easy way to know if they have Instant File Initialization Enabled or Not for their server. Honestly, this is a very simple question but there was no quick answer to this one before SQL Server 2016. However, if you are using SQL Server 2016 or later version of SQL Server, you can figure out the status of the instant file initialization pretty quickly.
It is interesting to see in SQL Server that same error message is raised due to multiple reasons. One such error is 9002. In this blog, we would quickly learn about the cause of error 9002: The transaction log for database ‘SQLDB’ is full due to ‘DATABASE_MIRRORING’
During my recent Comprehensive Database Performance Health Check Developer showed me a slow query which used ROWLOCK hint. The common understanding is that with the help of ROWLOCK hint SQL Server only locks a single row which eventually leads to performance but in their case, it was actually very much opposite. Let us see this scenario with a simple example.
During my recent engagement of Comprehensive Database Performance Health Check, Sr. DBA asked if it is possible to run SQL Server on multiple TCP Ports. The answer is Yes, it is very much possible.
In today’s blog we are going to talk about the SQL Server feature which actually exists for a quite a while but interestingly enough it is not known much. Let us have a quick introduction to startup procedures.
Question: How Old Version of SQL Server Running on Server?