June 30, 2014 at 12:32 pm
If only someone would write a book or article on a searchable, networked platform about this sort of thing.
June 30, 2014 at 12:39 pm
I understand the issue with the NOLOCK hint but what is wrong on the first line?
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
June 30, 2014 at 12:41 pm
Nothing, just obfuscating actual code.
June 30, 2014 at 12:41 pm
June 30, 2014 at 11:07 pm
sqldriver (6/30/2014)
If only someone would write a book or article on a searchable, networked platform about this sort of thing.
I might be missing the question but this type of thing is in Books Online.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2014 at 11:41 pm
Luis Cazares (6/30/2014)
Am I missing something in here?
+1
July 1, 2014 at 2:45 am
What exactly is wrong with updating a column to NULL?
The Nolock hint will be ignored since it's on the target table for an update (that should be documented in BoL)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 1, 2014 at 5:00 am
Yeah, if that equals NULL was in the WHERE clause I'd be laughing my bottom off.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 1, 2014 at 7:53 am
Tough crowd. I thought the NOLOCK on an update was amusing.
July 1, 2014 at 8:10 am
sqldriver (7/1/2014)
Tough crowd. I thought the NOLOCK on an update was amusing.
But of course it is.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 1, 2014 at 8:26 am
This was in the same query where someone had a non-clustered index on a bit column with "_V2" in the name, I guess insinuating that there was a "_V1" which this was superior to, in some way. Maybe the last index was on the column they were making NULL? I don't know. This just seemed like the right place to blow off some steam about the situation. The worst part about these things making it into production is that it takes forever to get them out.
July 1, 2014 at 9:13 am
sqldriver (7/1/2014)
Tough crowd. I thought the NOLOCK on an update was amusing.
BWAAA-HAAA!!! Ok... I get it. It wasn't a question... it was a statement about something that you found in code. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply