April 1, 2006 at 9:23 am
Not sure anyone has same problem. We found when we run the stress test (using MS stress test tool - ostress). When connections above 300, it throws 'SQL server not available' randomly. This is co-incide with the problem we are facing in our prod. environment from the Web server. But, now we know problem is not on the Web server but SQL related. The stress tool are running from the physical SQL server server DOS command console
Below is the stress test script
ostress.exe -SSQLSrv -Uusername -Ppassword -dDBName -Q"select top 10 * from tablename (nolock)" -n300 -r50 > local.txt
Anyone has any idea ?
April 3, 2006 at 10:37 am
Have you watched your performance counters?
Perhaps the server is too busy with I/O or something else.
April 3, 2006 at 10:54 am
110% sure is not the case (I/O), we're able to re-produce the problem on various system, H/W ranging from SCSI 3 to fiber to EMC. It sounds more like a setup issue somewhere.
April 4, 2006 at 10:04 am
Have you tried increasing/decreasing max worker threads?
April 5, 2006 at 6:27 am
Sure did, bumped from default 25 to 500, same issue.
April 5, 2006 at 6:27 am
Sure did, bumped from default 25 to 500, same issue.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply