December 18, 2016 at 11:12 am
Dear All,
How do i capture the slowness in query execution due to external factor, for instance any config change of underlying network or storage system.
To give a background of the issue, we had a scenario where all the queries in production environment started getting timed out from the application, however on database side we didn't find any issue with respect to index fragmentation, or any blocking/deadlock process and even thru wait stats not much was revealed that would raise a concern.
Our database are hosted in failover cluster environments.
Finally after lot of investigation it was found out the NIC drivers on the node on which Sql server was hosted was corrupted, so after reinstalling all the drivers the application started behaving normally.
So from a Sql Server database perspective to avoid such kind of scenario, is there any workaround or process or System defined object's (within database) that will help to capture and monitor key metrics details of underlying infrastructure where it is hosted so that any change in future can be tracked easily.
Let me know if there any other workarounds .
Thanks in advance.
Cheers!
Sam
December 18, 2016 at 2:35 pm
To be honest, you shouldn't have to do this with a system provider. They should have online diagnostics that check for this type of thing several times an hour. Not only should they detect it without any complaint by you but they should automatically just fix it without having to be notified by you that something isn't right.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply