Viewing 15 posts - 34,861 through 34,875 (of 59,102 total)
HowardW (2/28/2011)
sqlchanakya (2/28/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2011 at 8:06 pm
Colleen M. Morrow (2/28/2011)
Updates to fields not covered by the index would not cause any extra overhead of maintaining the index, so no concerns there.
"It Depends". If...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2011 at 7:57 pm
I know this is of no help and I apologize for that but I have to know... A billion+ byte SQL Script? What on Earth does it do?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2011 at 7:31 pm
BenWard (2/28/2011)
having done some testing using insert instead of union is VASTLY quicker and requires less re-write of our existing programs so we'll probably end up...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2011 at 7:22 pm
Gosh... if it's only running 100 times in 5 minutes, try adding OPTION(RECOMPILE) to the offending statement and you'll likely be done with the problem.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2011 at 7:14 pm
magasvs (2/28/2011)
Something else important that you should request - installation media for all versions of SQL Server installed in company.
And proof of licensing.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2011 at 6:49 pm
Craig Farrell (2/28/2011)
.... AAAAaaaaand I'm in trouble again....
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2011 at 6:05 pm
gregory.anderson (2/28/2011)
Jeff Moden (2/21/2011)
gregory.anderson (2/18/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2011 at 5:46 pm
Craig Farrell (2/28/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2011 at 5:37 pm
The hierarchical examples of Recursive CTE's in BOL aren't that bad and they aren't actually full blown RBAR because they process full levels at a time instead of just one...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2011 at 5:11 pm
Eric M Russell (2/28/2011)
Jeff Moden (2/25/2011) . . .
You're locked in a cell with a steel floor. At the center of the room is a pipe with massively thick...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2011 at 7:46 am
SQLkiwi (2/27/2011)
Jeff Moden (2/27/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2011 at 7:36 am
Thanks, Paul.
I agree... in particular, I saw that 70% sort on the second use of the Tally Table and believe it would go away if we simply wrote the results...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2011 at 6:55 am
Craig Farrell (2/27/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2011 at 6:48 am
I was going to post that the result table and the related methods for this code article are nearly identical to what full-text-search (FTS) does but I see that folks...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2011 at 6:34 am
Viewing 15 posts - 34,861 through 34,875 (of 59,102 total)