July 13, 2009 at 3:32 pm
Paul White (7/13/2009)
GilaMonster (7/13/2009)
tatcalltype ='null'Why.....Oh Lordy. I just found the full line:
update Auditdata set tatcalltype = 'null' where tatcalltype is null:sick:
I was referring to one of the other of his threads, the one that Dave posted.
SELECT <lots> FROM <somewhere> WHERE tatcalltype = 'null' AND <other conditions>
Done, apparently, because 'null' is faster than NULL
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 13, 2009 at 3:42 pm
GilaMonster (7/13/2009)
I was referring to one of the other of his threads, the one that Dave posted.
SELECT <lots> FROM <somewhere> WHERE tatcalltype = 'null' AND <other conditions>
Done, apparently, because 'null' is faster than NULL
Yes hes only got 15million rows , apparently selecting 14.7 million and would like it to run fast.
*magic wand being waved* 🙂
July 13, 2009 at 5:09 pm
GilaMonster (7/13/2009)
Done, apparently, because 'null' is faster than NULL
But only if you use little letters (less aerodynamic drag = faster!)
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
July 13, 2009 at 6:09 pm
Paul White (7/13/2009)
GilaMonster (7/13/2009)
Done, apparently, because 'null' is faster than NULLBut only if you use little letters (less aerodynamic drag = faster!)
...then he should use cursive...
---------------------------------------------------------
How best to post your question[/url]
How to post performance problems[/url]
Tally Table:What it is and how it replaces a loop[/url]
"stewsterl 80804 (10/16/2009)I guess when you stop and try to understand the solution provided you not only learn, but save yourself some headaches when you need to make any slight changes."
July 13, 2009 at 6:52 pm
jcrawf02 (7/13/2009)
Paul White (7/13/2009)
GilaMonster (7/13/2009)
Done, apparently, because 'null' is faster than NULLBut only if you use little letters (less aerodynamic drag = faster!)
...then he should use cursive...
You mean if you change fonts you get better performance? Holy smokes! I've got to get some edits into the chapter on tuning...
----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software
July 13, 2009 at 7:01 pm
Grant Fritchey (7/13/2009)
jcrawf02 (7/13/2009)
Paul White (7/13/2009)
GilaMonster (7/13/2009)
Done, apparently, because 'null' is faster than NULLBut only if you use little letters (less aerodynamic drag = faster!)
...then he should use cursive...
You mean if you change fonts you get better performance? Holy smokes! I've got to get some edits into the chapter on tuning...
It definitely improves performance if you use a smaller font as it takes less storage space.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
July 13, 2009 at 7:16 pm
[font="Verdana"]I guess typographical ligatures fall into the advanced performance optimisation techniques.[/font]
July 13, 2009 at 7:24 pm
Jack Corbett (7/13/2009)
Grant Fritchey (7/13/2009)
jcrawf02 (7/13/2009)
Paul White (7/13/2009)
GilaMonster (7/13/2009)
Done, apparently, because 'null' is faster than NULLBut only if you use little letters (less aerodynamic drag = faster!)
...then he should use cursive...
You mean if you change fonts you get better performance? Holy smokes! I've got to get some edits into the chapter on tuning...
It definitely improves performance if you use a smaller font as it takes less storage space.
Good point. Queries involving a Unicode NULL can bring a server to its knees.
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
July 13, 2009 at 7:41 pm
Grant Fritchey (7/13/2009)
You mean if you change fonts you get better performance? Holy smokes! I've got to get some edits into the chapter on tuning...
[font="Verdana"]I'm also thinking you could see a dramatic difference in performance, depending on which font you use. I wonder what would happen if you chose Wingdings?
[/font]
[font="Wingdings"]null[/font]
[font="Verdana"]Scary!
[/font]
July 13, 2009 at 11:32 pm
jcrawf02 (7/13/2009)
Paul White (7/13/2009)
GilaMonster (7/13/2009)
Done, apparently, because 'null' is faster than NULLBut only if you use little letters (less aerodynamic drag = faster!)
...then he should use cursive...
i think he already tried shouting and swearing at the server. Didnt post the query plan though , so cant be sure:-)
July 14, 2009 at 1:35 am
Dave Ballantyne (7/13/2009)
GilaMonster (7/13/2009)
I was referring to one of the other of his threads, the one that Dave posted.
SELECT <lots> FROM <somewhere> WHERE tatcalltype = 'null' AND <other conditions>
Done, apparently, because 'null' is faster than NULL
Yes hes only got 15million rows , apparently selecting 14.7 million and would like it to run fast.
sp_configure 'Run queries fast', 1
Like the old turbo button on circa 286 machines.
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 14, 2009 at 2:23 am
I think my 486 DX2/66 had a turbo button - if I recall it ran at 33Mhz normally...
That query is easy:
SELECT
FROM
WHERE tatcalltype = 'null'
AND
OPTION (FAST ALL)
edit: stupid angle brackets! I give up - you get the idea
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
July 14, 2009 at 2:56 am
IIRC it wasnt a turbo button , it was a 'go-slow for compatibility' button. I think 'turbo' is a better marketing term though
July 14, 2009 at 3:05 am
Dave Ballantyne (7/14/2009)
IIRC it wasnt a turbo button , it was a 'go-slow for compatibility' button.
Yeah, it was. That was part (maybe too subtle) of my joke. It could be turned off for apps that ran too fast on the newer machines, but no one I knew then ever switched it off.
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 14, 2009 at 3:12 am
Paul White (7/14/2009)
edit: stupid angle brackets! I give up - you get the idea
Use the escape codes, not the brackets, unless you're writing actual xml. Markup's not allowed within the code blocks.
< and >
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
Viewing 15 posts - 6,601 through 6,615 (of 66,000 total)
You must be logged in to reply to this topic. Login to reply