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 |
|
coolerbob
Aged Yak Warrior
841 Posts |
 Posted - 2008-11-25 : 10:43:26
|
| We have a lot of users using the same sql login.I ran a test and used the same login to perform a high amount of transactions.I noticed a .net app trowing the following error:Database Error - TCP Transport-Level Error (Pool Cleared)A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) I did this a few times and it happened each time. There does seem to be a correlation.I wonder if this proves my theory. Is there a limit as to how many transactions one login can handle?If so, how do you address that? If you have a website with lots of users, you really don't want to be creating a login for every user... |
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2008-11-25 : 10:51:42
|
No. Each connection is unique.It seems rather that the SQL Server is so busy it can't monitor TCP request.Recently I developed an application for 400 simultaneous users. Works flawless.However I have countered your situation when doing backups, defragmentation routines or other resource intensive jobs.
E 12°55'05.63"N 56°04'39.26" |
 |
|
|
|
|
|
login best practice