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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-05-30 : 09:44:17
|
Matt writes "I have a stored procedure that simply executes 1 update statement. I call it from an ASP page in a for loop that does nothing but execute the stored proc for each multiple sets of data. When multiple users access the system deadlocks occur on a very frequent basis. I have tried the following:
SET TRANSACTION ISOLATION LEVEL READ COMMITTED (and then placed the update statement in a transaction) and this did not help the problem
I then tried SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED and the result was that no deadlocks occurred but if 20 rows were supposed to be updated only two successfully updated and no error message was thrown.
Is there a problem with rapidly calling the same stored procedure?
Details: NT 4.0, SQL Server 7.0
Thanks" |
|
|
|
|
|
Calling stored procedure from a for loop