April 9, 2009 at 2:19 am
Hi all,
we have a old application in our company, which is using SQL Server 2000 SP4.
Sometimes if a developer makes a SELECT on a table, this SELECT locks the table (but the SELECT was completed and only the result is shown) and everybody, who using this table in the app gets an Timeout.
What can I do to solve this problem ?
Thanks for all response
cya
Jens
April 9, 2009 at 2:46 am
if you can risk gost data in your select statement then you could change the code to use NOLOCK
Select * from table WITH (NOLOCK)
there are certain risks involved (possible missing rows, or duplicate rows) but if you evaluate your environment and any actions you are going to drive from this data that you select, then you might consider it a worthwhile fix
evaluate and consider carefully before implementing this though.
MVDBA
April 2, 2024 at 9:51 pm
This was removed by the editor as SPAM
April 9, 2024 at 9:01 pm
This was removed by the editor as SPAM
April 15, 2024 at 5:52 pm
This was removed by the editor as SPAM
May 15, 2024 at 9:38 pm
This was removed by the editor as SPAM
May 18, 2024 at 2:53 pm
This was removed by the editor as SPAM
August 23, 2024 at 7:22 am
This was removed by the editor as SPAM
September 27, 2024 at 6:51 pm
This was removed by the editor as SPAM
October 26, 2024 at 1:21 pm
This was removed by the editor as SPAM
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply