Hi All,

During our DR drill we found that the same code which used to run perfectly fine on our Primary Data Centre is running very slow on Disaster Recovery DB Server and there are Lot's of open transaction with sleeping status and waittype as 'AWAITING COMMAND'.

CPU, Memory and disk utilization are good. The ping reply between the app server and the DB server is well within the limit's even blocking is not their, also nothing is reported in the error logs.

What else could be the problem?

We are using SQL server 2014 STD 64 BIT on Windows Server 2012.

Hi Ashif,

For such issues, it has nothing to do with physical connection , it is just  logical connections  

This is resulted by different reasons , one of the most popular reasons is much waits relevant to the physical connection such as :

• CXPacketwaits resulted by much CPU waits
• PagaIOlatch_SH /PageIOlatch_ UP..etc resulted by ,uch IO waits
• Asynchronous network IO waits resulted by some Network issues

Therefore, I don't worry about these multiple logical connections themselves,, but you have to look after these waits interrelated with these connections

The reply that we are receiving between the APP server's and DB server's is 12MS.

Could this be the issue?