Login or Sign Up to become a member!
LessThanDot Site Logo

LessThanDot

A Technical Community for IT Professionals

Less Than Dot is a community of passionate IT professionals and enthusiasts dedicated to sharing technical knowledge, experience, and assistance. Inside you will find reference materials, interesting technical discussions, and expert tips and commentary. Once you register for an account you will have immediate access to the forums and all past articles and commentaries.

LTD Social Sitings

Lessthandot twitter Lessthandot Linkedin Lessthandot facebook Lessthandot rss

Note: Watch for social icons on posts by your favorite authors to follow their postings on these and other social sites.

Highly Rated Users

Forum
No Posts Rated

Top 50
Given
Received

Forum Statistics

Users
Members:
1877
Members Online:
3
Guests Online:
97

Total Post History
Posts:
81447
Topics:
18714

7-Day Post History
New Posts:
0
New Topics:
0
Active Topics:
0

Our newest member
AlicjaHYBCIA

Other

FAQ
All times are UTC [ DST ]

Google Ads

Suggestion: Identify (NOLOCK) as a problem for 2005+

Please wait...

Suggestion: Identify (NOLOCK) as a problem for 2005+

Postby SAinCA on Sat Jan 21, 2012 1:56 am

With READ_COMMITTED_SNAPSHOT ON available from SQL 2005 onwards, NOLOCK, typically a (horrible but necessary) workaround to eliminate blocking/contention in SQL 2000 OLTP solutions, should be removed wholesale as a normal practice (IMO).

Would you consider adding this as a code-investigation feature, to include triggers as well as the usual SPs and UDFs, please?

(Thanks for developing this utility - having inherited multiple databases with some awful tables and code, it has proven to be a quick and effective means of identifying dross.)
User avatar
SAinCA
Newbie
Newbie
LTD Bronze - Rating: 3
 
Posts: 4
Joined: Fri Jan 20, 2012 7:45 pm
Location: Yorba Linda, CA. USA
Unrated