Driver Error 12031 Connection - Reset

[Guest_imported]

While accessing a web site i am getting " Driver Error -12031, Connection - Reset " Could u please tell me what can be the reason for this. The error usually occur when number of users are accessing the same site.....

 

[tlbroadbent]

I think 12031 is an Internet event code. The connection reset may or may not be related to SQL Server. Do you have reason to believe that SQL Server is the cause or a contributor to this message? The Internet connection could be reset for any number of reasons.

SQL Server may be the problem if the load is causing SQL Server response to slow signifcantly. The Web server may reset connections that timeout in SQL Server. I have seen that happen on long running queries. Of course, resets could occur because of other limitations in the environment. Terry

http://members.home.net/tlbroadbent/sqlarticles.htm

"I shall try to correct errors when shown to be errors, and I shall adopt new views so fast as they shall appear to be true views." - Abraham Lincoln

 

[Guest_imported]

After analyzing the system again, it seems the error is only with SQL Server. Can you please suggest some ways to handle the problem. What are the possible ways to optimize SQL server. Regarding Internet Connection Reset after how much time does a
connection reset occur.

Can i change some settings on my browser to avoid Connection Reset.

 

[tlbroadbent]

When you say, "the error is only with SQL Server," do you mean that you've determined that applications accessing SQL Server are the only ones affected by the resets? From your first post, I assume the frequency of resets increases as the load on SQL Server increases.

What you need right now is analysis to determine the causes of the SQL slowdown. Things to look for[ol][li]Locks - run sp_lock, sp_who2 or use Enterprise Manager (EM) to view locks. Locks cause processes to wait for the lock to be freed. (Read faq183-714 and faq183-767.)

[li]Long running queries - Poor design is usually the culprit but locking, poor indexing, inadequate hardware.

Look for queries that create Temporary tables. Improper use of temp tables can really slow things down. Read

http://www.sql-server-performance.com/nb_avoid_bottlenecks.asp

Look for queries that use cursors. Cursors are very inefficient. Usually, cursors are ysed to step through data, one row at a time. SQL is designed to deal with sets of data. Therefore, procedures using cursors can often be rewritten to use relationships and avoid the overhead of cursors.

[li]Proper indexing on tables - you can have too few or too many indexes! Poor indexing can lead to locking and slow running queries.

[li]Use performance monitor to view cache hit ratio, processor usage, disk usage, disk latency, ... There are lots of factors involved.[/ol]I've only touched on a few items. There are many articles available from Microsoft and others that discuss performance. I've listed a few below. Good luck.

faq183-768

http://www.swynk.com/friends/boyle/speed_select.asp

http://www.swynk.com/friends/mcgehee/developers_tuning_tutorial.asp

http://www.sqlmag.com/Articles/Index.cfm?ArticleID=16272

http://www.swynk.com/friends/boyle/savingspace.asp

Terry

http://members.home.net/tlbroadbent/sqlarticles.htm

"I shall try to correct errors when shown to be errors, and I shall adopt new views so fast as they shall appear to be true views." - Abraham Lincoln