tag:blogger.com,1999:blog-36914164.post1549480887867309747..comments2023-05-03T04:43:30.936-07:00Comments on Persistence of Vision: Using JOIN, NOLOCK, and Table (Index) Hints TogetherRob Garrisonhttp://www.blogger.com/profile/09779841540941950357noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-36914164.post-40718815696198335092013-12-23T12:05:34.531-08:002013-12-23T12:05:34.531-08:00Sven, I added a bit about NOLOCK issues at the ver...Sven, I added a bit about NOLOCK issues at the very beginning of the post.Rob Garrisonhttps://www.blogger.com/profile/09779841540941950357noreply@blogger.comtag:blogger.com,1999:blog-36914164.post-78635757301642094502013-12-16T14:57:20.915-08:002013-12-16T14:57:20.915-08:00I worded it a bit harshly, the comment of some ran...I worded it a bit harshly, the comment of some random guy going "oh great awesome" kind drove me into a mild depression. So, i'd like to appologize for that, the wording.<br /><br />I too worked at a company where with nolock was the defacto default on a query, cause yeah, no locking, so faster, so better.<br /><br />Its the most dangerouse query hint I can think of, closely followed by join hints. <br />To many use hints without understanding the implications because they read some out of context snippet on the internet. Could you include a little warning about the dangers of dirty reads in your post ? It lacks context, with your reply it makes a lot more sense, but not everyone reads all the coments.<br />Anonymoushttps://www.blogger.com/profile/12697838173304646880noreply@blogger.comtag:blogger.com,1999:blog-36914164.post-72783488380862828112013-12-16T14:36:21.138-08:002013-12-16T14:36:21.138-08:00Sven, I completely understand that there are issue...Sven, I completely understand that there are issues with NOLOCK and table hints. In this particular case, I was using the hint to test the performance difference between two different indexes. Once I had proven which one was the best index design, I dropped the second index and removed the hint.<br /><br />And NOLOCK? I was working in an organization where NOLOCK was expected for every reporting query. That was a battle that had been fought and lost before I got there.Rob Garrisonhttps://www.blogger.com/profile/09779841540941950357noreply@blogger.comtag:blogger.com,1999:blog-36914164.post-20063640726065240072013-12-16T13:47:40.290-08:002013-12-16T13:47:40.290-08:00yes, go ahead and blindly use with(nolock) without...yes, go ahead and blindly use with(nolock) without knowing anything about how that blackbox of a dbms works. Who ever wanted to have results of a query where you dont have to question the validity of the returned data anyway.<br /><br />Guys, don't use query hints while you don't even have a good grasp of the pritty basic tsql syntax. You are going to shoot yourself in the foot so hard your leg is going to be missing. Especially on with(nolock). Just google with(nolock) and read up on it....Anonymoushttps://www.blogger.com/profile/12697838173304646880noreply@blogger.comtag:blogger.com,1999:blog-36914164.post-72046257878475234042012-07-17T07:28:54.319-07:002012-07-17T07:28:54.319-07:00awesome. many thanks for this informationawesome. many thanks for this informationAnonymousnoreply@blogger.com