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 |
|
johntaylorny
Starting Member
1 Post |
 Posted - 2010-08-05 : 13:48:59
|
| I'm hoping someone can help me with a problem we've had for over a year.We have a web site that interacts with a database (Sql Server). People create accounts on the web site, get a username, log in and then their progress is saved in the db.The problem we have is that when a large amount of people set up accounts and are hitting the db within a short period of time the db gets screwed up and on the web site it says "runtime error occured" whenever someone on the site tries to access a feature that requires interaction with the db. We moved the db to a large hosting company and to my dismay, the same thing happens when things get busy.Any idea what could be causing this. The only bandaid fix is that we recycle the db and that fixes it. |
|
|
mfemenel
Professor Frink
1421 Posts |
Posted - 2010-08-05 : 15:19:43
|
| Off the top of my head the first 2 things i can think of are connections not getting released? Over indexed tables causing locking on too many inserts? Do you use xml with prepare document? I've seen that cause a memory leak without a corresponding remove document before.Mike"oh, that monkey is going to pay" |
 |
|
|
|
|
|
server / runtime errors when db busy