Performance of sqlservercentral.com
-
Isn't this site the last place that I should see an error like this?
http://www.sqlservercentral.com/scripts/savescript.asp?scriptid=1056
Microsoft OLE DB Provider for ODBC Drivers error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired
/scripts/lib.asp, line 400
Let's see, there are threads on sizing, tuning, ...
-
Doh!
Actually you are correct, but we have other constraints, bandwidth, money, and you guys hammer the bejeezus out of this place. We're averaging (5 min avg, over the last 6 months) > 1.1Mbps. The load (on occassion) goes through the roof and peaks the 1.5 that we have. And yes, there are some issues with ASP.NET and SQL Server on the same box. Not recommended, pointed out over and over, but it's a constraint (for now).
New box is in the colo, getting configured and tested as I write this and the db and web will get separated out shortly.
Thanks for giving us the problem though.
-
Hi Steve,
I'm also getting the same type of error "Microsoft OLE DB Provider for ODBC Drivers error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired " on one of the pages I had hosted. Could you please let me how to rectify the problem. I'm using Classic ASP which creates files on the basis of SQL results.
Hope to get appropriate solution from you.
Thanks.
-
Buy a bigger box
The timeout occurred because the db and web were on the same box and we were getting overloaded. We separateed them out with new hardware and haven't had the issues.
You can increase the timeout on ASP, I think there's a setting in ADO to do this or tune the queries to run quicker as well.
-
Steve, lately though I have been getting a lot of OutOfMemory exceptions. Something you are aware of?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply