Urgent, problem of Accessing database table 1

[TC2000]

Error Message in SQL server error log :

Error : 17824, Severity: 10, State: 0
Unable to write to ListenOn connection '\\.\pipe\sql\query', loginname 'ate_sea', hostname ''.
OS Error : 232, The pipe is being closed.
Error : 1608, Severity: 21, State: 2
A network error was encountered while sending results to the front end. Check the SQL Server errorlog for more information.


When one client use our application program to access one table of SQL Server Database from the terminal, the system likes hanging and harddisk of SQL Server likes searching data to flash continously. 5 mins later, the terminal will get the data. In normal state, data should access around 5-10s. This application program is used by more than 40 clients at the same time.
This is a very very very big problem.
Please help me solve this problem, thank you!!!

 

[Bernadette]

Hi There

I had this problem on one of my servers and the cause was a deadlock. Check your SQL Server to see if there is any deadlocks and delete the blocking process.

Hope this helps Bernadette

 

[tlbroadbent]

If the problem is a deadlock, it will ilkely reoccur. You'll need to do some work to eliminate the cause of the deadlock. If you find you have a deadlock problem, post here and I'll provide some resources for helping eliminate deadlocks. Terry

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

 

[Bernadette]

Hi Terry

Can you post a link to the resources for helping eliminate deadlocks please... might help with my problem

Thanks in advance Bernadette

 

[tlbroadbent]

Here are some resources that provide help with deadlocking issues in SQL Server.

Tips from Microsoft
(

http://www.microsoft.com/sql/default.asp)

INF: Understanding and Resolving SQL Server 7.0 or 2000 Blocking Problem

http://support.microsoft.com/support/kb/articles/Q224/4/53.ASP

Tips from SQL-Server-Performance.Com
(

http://www.sql-server-performance.com)

Tips for Reducing SQL Server Locks

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

SQL Server Lock Contention Tamed: The Joys Of NOLOCK and ROWLOCK

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

Tips from SWYNK.Com
(

http://www.swynk.com/sysapps/SQL.asp)

Transactions, locking and concurrency in SQL Server - Part I

http://www.swynk.com/friends/sharma/locking.asp

http://www.swynk.com/friends/sharma/locking2.asp

Terry

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

 

[Bernadette]

Thanks very much Bernadette

 

[TC2000]

Hi there,

Could anyone tell me how to check the SQL Server to see if there is any deadlocks and how to delete the blocking process?

Should I issue the kill command?
Thanks
Keith

 

[tlbroadbent]

You can check for blocks using Enterprise manager.

From BOL:

To view the current locks

1- Expand a server group; then expand a server.
2- Expand Management; then expand Current Activity.
3- Expand:
a- Locks / Process ID to view the current locks for each connection.
b- Locks / Object to view the current locks for each object currently locked.
4- In the console tree, click the connection (SPID) or object to view. The current locks for the connection or object are displayed in the details pane.

From Query Analyzer you can run sp_who2 to view current processes and blocks. Terry

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