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.

 All Forums
 General SQL Server Forums
 Data Corruption Issues
 Concurrency issue in result returned from stored p

Author  Topic 

joship2
Starting Member

1 Post

Posted - 2007-12-11 : 08:10:18
I am working on application developed in ASP.NET 2.0 that uses lots of stored procedures from the SQL Server 2000 backend database.When the app is under load you occasionally see incorrect data returned to the page after running stored procedures.

All the stored procedures have been tested and appear to be fine. it's as if under load the returned data from the stored procedures is getting 'mixed' with another concurrent session.
Please let me know what could be the reason behind it

harsh_athalye
Master Smack Fu Yak Hacker

5581 Posts

Posted - 2007-12-11 : 08:13:02
Have you included transaction processing in your SPs?

Harsh Athalye
India.
"The IMPOSSIBLE is often UNTRIED"
Go to Top of Page

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2007-12-11 : 10:05:04
you're probably using a nolock hint somewhere... or a read uncommited transaction isolation level.
or like harsh said, you're not using transactions.

_______________________________________________
Causing trouble since 1980
blog: http://weblogs.sqlteam.com/mladenp
SSMS Add-in that does a few things: www.ssmstoolspack.com <- new version out
Go to Top of Page

joship
Starting Member

2 Posts

Posted - 2007-12-11 : 10:43:06
Hi ,

Thx for your reply. We are not using transaction processing (Begin trans,commit or rollback trans) in stored proc. However it is creating problem only in case of heavy load otherwise its working fine. Can you please explain why it is happening in case of heavy load only ?
Go to Top of Page

harsh_athalye
Master Smack Fu Yak Hacker

5581 Posts

Posted - 2007-12-11 : 10:47:56
It happens so that during heavy multiple users are accessing the database and you are doing nothing to prevent two users from accessing same set of data.

Harsh Athalye
India.
"The IMPOSSIBLE is often UNTRIED"
Go to Top of Page

joship
Starting Member

2 Posts

Posted - 2007-12-11 : 11:38:45
harsh thx for ur reply. so do you mean to say we need to implement transaction isolation level in stored procedure ?
Go to Top of Page

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2007-12-11 : 11:41:21
of course. at least read commited. and no using with(NOLOCK) query hints

_______________________________________________
Causing trouble since 1980
blog: http://weblogs.sqlteam.com/mladenp
SSMS Add-in that does a few things: www.ssmstoolspack.com <- new version out
Go to Top of Page
   

- Advertisement -