We have an application that was orginally set up using ASP Classic with one user name used to access SQL Server on an application with many users.
The application is now a combination of ASP & ASP .NET pages. The application pool has increased from lets say 200 to 1000. It seems that the session time out cannot be controlled. No matter how we set it users continue to be timed out inadvertantly. We still have one username and every user connects to SQL Server using this same user name and you can see them all listed with the same user name when running sp_Who. Have we surpassed the ability to use the one username and the application session does not know which user to time out. Signed, Newbie To unsubscribe from this group, send email to dotnetdevelopment+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
