What is a "suspended" process status 1

[seaport]

When I run sp_who2 on my sql server 2005, I got several processes "suspended" in a user database. I do not know what it means exactly and how to deal with it. What I can see is that,
1. This is not good.
2. Once a process is suspended, it stays suspended until the front-end Access database is close.
3. A suspended process blocks another process, which in my case the front-end Access cannot insert a record.

Could someone explain to me what is "Suspended", how to deal with it, or maybe more important, how to avoid it?

Thanks in advance.

Seaport

 

[jasper06]

Hi Seaport

This is an issue that is new in SQL Server 2005, and is only exposed under specific conditions – namely, the use of the x64 version of SQL Server 2005 and the execution of large ad hoc query batches. Unfortunately, the memory that is used to store the execution plans for those ad hoc queries is not trimmed aggressively enough in the x64 version, and as a result we see more and more connections having to wait for memory allocations before they can continue. If any connection is suspended for more than 30 seconds, the application terminates the connection by reporting that the command currently executing has timed out.
This issue has been previously identified and is fixed in the upcoming service pack release (SP2) for SQL Server 2005
Possible Solutions:

1. Sp2


5) 2. create a job that manually frees the memory that is being consumed by query plans through the use of the DBCC FREEPROCCACHE command. The documentation for this command states that “freeing the procedure cache causes, for example, an ad hoc SQL statement to be recompiled instead of reused from the cache.” (

http://msdn2.microsoft.com/en-us/library/ms174283.aspx)

 

[seaport]

Thanks, Jasper,

My SQL Server is x32 version. But I asked the administrator to install the SP2 anyway.

Still, my question is the concept of "suspended". In the status column, I got the following status:
- Background (only in master db so I am not interested in.)
- sleeping (I guess it is the same as being idle.)
- Runnable (strange word, I guess it means that "it has been executed successfully.")
- Suspended (I guess it means failed. But if a sql command "failed," why does it affect/block other commands? Maybe it means "still being executed and sql server does not know how long it takes"?

Seaport