mickyT (7/9/2013)
And in the category of just plain silly... OVER (ORDER BY (SELECT 'I can''t think of anything better to put in here toocause this to be a string larger in bytes than I would expect the previous examples
to have, so I''ll just keep on typing until the carpel tunnel sets i'))
the size balloons out to 1,140B including the carriage returns:-)
That does nothing for my Carpal Tunnel.
Neither does this:
SELECT TOP 10000000 @Bitbucket=ROW_NUMBER() OVER (ORDER BY (SELECT CAST(0 AS NVARCHAR(MAX))))
FROM sys.all_columns ac1, sys.all_columns ac2, sys.all_columns ac3
But oddly it seems to perform in the same approximate time as the previous 3.
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St