Hi All,
I'm running MSSQL2005 as the backend for my web apps.
If I open the activity monitor I can see some open transactions on some of the DB's.
The details in 3 DB's are as follows:
SET TRANSACTION ISOLATION LEVEL READ COMMITTED
FETCH API_CURSOR000000000004CA39
FETCH API_CURSOR000000000005AA7B
and the status on all is sleeping.
Occasionally a DB will jam up with a whole bunch of locks. The only way to fix is to kill the locked process's and restart the web app which inadvertently leads to some data loss for the user.
I'm not sure if any of these open transactions end up causing the lock up.
I have selected all the default options when I setup SQL2005 and the databases.
Anyone got any suggestions?
Cheers,
Kevin
Topic: MSSQL2005 (Read 3004 times)