|
|
|
SSChasing Mays
      
Group: General Forum Members
Last Login: Today @ 10:00 AM
Points: 643,
Visits: 1,248
|
|
Hi folks, I'm a little stumped here and would be curious as to what may be causing some application timeouts on our database.
We have a database which customers use to manage their accounts and update their settings/orders/etc. throughout the day without issue. However, a few months ago, we did a SAN firmware update and weird timeouts occurred since then. On the SQL side, the logs show: SQL Server has encountered 1 occurence(s) of I/O requests taking longer than 15 seconds to complete on file ... This only seems to happen when the DBCC Checkdb kicks off. Currently, it's running with the PHYSICAL_ONLY option so in theory does less. The only time of day these timeouts seem to occur is during that maintenance window. I'm doing one more test where I will completely disable the maintenance jobs for the next couple nights and see if anything occurs.
We are pretty confident that there is nothing wrong, per se, with the SQL 2005 server itself and it is on a 64-bit windows cluster with 8-cores. It is on Service Pack 2 (I know, no excuse to not be on SP3, but why would this occur after a SAN firmware update).
I have some possible solutions I could try on the SQL side: 1. Update to SP3/CU5 (most recent) 2. Double-check the MSDTC and cluster settings. (we did notice some MSDTC errors one night, but may have been coinciding with some network maintainence that occurred around that time).
Anything else anyone would recommend would greatly be appreciated.
Thanks.
Gaby ________________________________________________________________ "In theory, theory and practice are the same. In practice, they are not." - Albert Einstein
|
|
|
|