Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
How to resolve the lock
Message
From
16/12/2004 17:49:12
 
 
To
09/12/2004 02:08:31
Rene Lovino
Bigfoot Global Solutions, Inc
Cebu, Philippines
General information
Forum:
Microsoft SQL Server
Category:
Database management
Miscellaneous
Thread ID:
00967937
Message ID:
00969874
Views:
45
>Hi All,
>
>My SQL Server database always suffering a process that block by other process.
>I can check it using SP_WHO and SP_WHO2 stored procedure.
>There are so many process ID that is idle by still block some other process that is some other process cannot execute successfully.
>The application was developed using JAVA but I don't know JAVA. My rule in the database is a DBA.
>I'm a new DBA since I'm a developers from my previous job but I don't know JAVA since I'm only using microsoft products.
>
>My question is, Is there a way to automatically kill the idle process that block other process.
>As of now I have manually kill the process using the KILL command to allow other process to execute.
>What I have done is to check the available process in the DB Server and determine which process causes the lock and kill it manually.
>Our application always suffering a deadlock because of idle process that block other process.
>We are on the process of investigating it. This is my big puzzle that needs to resolve.
>I have already check my SQL Server and OS configuration and there is no problem on my configuration.
>
>Anybody can help me to resolve my problem.
>
>
>Thanks,
>
>
>Rene

Set a Timeout.

You can use a Connection interface timeout ( this is a job timeout )
or a T-SQL lock timeout ( more precise )

* ODBC
sqlsetpro(m.stmt,"ConnectTimeOut",5)
* T-SQL
SET LOCK_TIMEOUT timeout_period


Fabio
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform