G
Guest
Hello, I don't know much about SQL Server processes/SPIDs but everytime our
web app creates a ADO.NET connection and closes it, the SPID is still hanging
around in "sleeping status" well after it's closed in the ADO.NET code.
Is this normal or I am making database calls inefficiently?
I also thought mutiple connection w/ the exact same connection string
becomes pooled. If pooled, will that not affect the number of SQL SPIDs
created.
Should I be concerned about the number of SPIDs the app is producing or is
this normal?
Thanks in advance,
Jim
web app creates a ADO.NET connection and closes it, the SPID is still hanging
around in "sleeping status" well after it's closed in the ADO.NET code.
Is this normal or I am making database calls inefficiently?
I also thought mutiple connection w/ the exact same connection string
becomes pooled. If pooled, will that not affect the number of SQL SPIDs
created.
Should I be concerned about the number of SPIDs the app is producing or is
this normal?
Thanks in advance,
Jim