Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
drumm
Starting Member
14 Posts |
 Posted - 2002-07-11 : 10:34:27
|
| We have an ASP page which is called sometimes up to several times pr. second. The ASP page calls a stored procedure, which uses transaction and locks to avoid dirty writes and reads in the database.The SP looks something like this:----------------------------------------------------------------------alter procedure sp_getIT[...]set xact_abort onset transaction isolation level repeatable readbegin transaction [...]select @intOldOwnerID = value from xmitvalues (updlock)where xmitattribut = '1'[...]update xmitvalues [...][...]commit transaction----------------------------------------------------------------------However, if I check my processes in master..sysprocesses, I have multiple (sometimes up to 40) processes with waittype 0x0000, lastwaittype WRITELOG and status SLEEPING. These processes seem to hang around. Can anything be done to make prevent them from doing this?Thanks in advance,Thomas |
|
|
setbasedisthetruepath
Used SQL Salesman
992 Posts |
Posted - 2002-07-11 : 10:54:17
|
| This isn't a SQL Server issue per se; the ASP code acquiring database connections is not releasing them.Jonathan Boott, MCDBA |
 |
|
|
drumm
Starting Member
14 Posts |
Posted - 2002-07-12 : 03:31:02
|
| Of course!I spent so much time looking for the explanation that I missed the obvious, IIS is using connection pooling...Thanks! |
|
|
|
|
|
|
transaction causes multiple WRITELOG processes