We have a problem with orphaned user spid's in MS SQL Server when we run a crystal report through a DLL called from ASP code. The spid is initiated when the report call is made, but never clears out. Interestingly, the database association to the spid changes from the database the report is run against to the default database for the user ID when the report is completed. I assume that means that a database close is being implictly performed, but no SQL Server logoff (explicit or implicit) takes place.
I'm very interested in any advice anyone can lend.
I'm very interested in any advice anyone can lend.