September 6, 2006 at 9:36 am
Would anyone know what the default MAXTRANSFERSIZE is for SQL Server 2000?
SQL Server has encountered 16 occurrence(s) of IO requests taking longer than 15 seconds to complete on file [H:\MSSQL\Data\tempdb_Data_05.NDF] in database [tempdb] (2). The OS file handle is 0x000005B8. The offset of the latest long IO is: 0x00000040a6e000
September 7, 2006 at 7:10 am
Are your servers configured for NIC Teaming? If so, try breaking them and see what happens. We've had a similar case during restores of large databases 300-400 GB and seeing your mentioned error plus various other "no sufficient resources available" errors. We disabled the NIC teaming and saw the problem go away.
I've also seen this happen quite frequently whenever a disk drive fails and a rebuild kicks in. Check to see if there have been any drive failures recently. We had a bad array enclosure which apparently would blow out a drive every couple of days. HP replaced the backplane of that enclosure and we haven't had any drive failures since. (knockknock)
September 7, 2006 at 8:12 am
I had this problem and turning off the /3GB switch fixed it.
Joshua Perry
http://www.greenarrow.net
September 7, 2006 at 2:13 pm
Passed this on to our server guy, he said we use NIC Teaming, but only in a smart failover configuration, not load balancing. No drive failures.
8 SAN attached servers are involved, with memory sizes ranging from 3 GB to 16 GB, so we want to use as much memory as possible for SQL Server.
I emailed a performance & tuning instructor, he didn't know what the MAXTRANSFERSIZE default is either, but suspects it's memory dependent.
Anyway, HP is having us test running backups with MAXTRANSFERSIZE parameters & preferred path settings, to try to avoid huge I/Os suspected of causing the timeouts.
September 7, 2006 at 2:15 pm
Oops, I meant to say he suspects the MAXTRANSFERSIZE default is hardware dependent, not memory dependent.
September 8, 2006 at 6:57 am
I would check the event log for any errors or warnings related to NIC teaming. If there are any, this may very well be a probable cause.
September 8, 2006 at 11:31 am
Nothing in the event logs anything like that.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply