Viewing 15 posts - 40,231 through 40,245 (of 59,098 total)
Steve Jones - Editor (1/18/2010)
And buy him a few lunches. That will go a long way when you call later.
If (s)he is a person who likes to occasionally imbibe, a...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 19, 2010 at 8:35 pm
BWAA-HAA! Finally! I read a whole post before jumping in! 😀 Nicely done, John.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 19, 2010 at 8:33 pm
The Dynamic Crosstab article that Lutz mentions above very specifically has a "year long" example that should do the trick for you. All you have to do is change...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 19, 2010 at 8:31 pm
Thought I'd throw a different slant on that and also add a couple of optimizations for both VARCHAR(8000) and single character delimiters...
CREATE FUNCTION dbo.DelimitedSplit
/**************************************************************
Purpose:
Split a given string...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 19, 2010 at 8:20 pm
Just a clarification... use of NTEXT in 2k does NOT allow you to violate the 8060 rule. The data that's normally stored in the table is a numeric pointer...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 19, 2010 at 7:30 pm
Thanks for the feedback and I hope you get well soon.
As a side bar, if "total cost" is coming from the execution plan, then possibly a bad test. I...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 19, 2010 at 6:07 pm
Nicely done, Stephen. Well written and straight to the point.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2010 at 9:56 am
jdurandt (1/18/2010)
I benchmarked EXCEPT vs WHERE NOT IN (SELECT .....), and for my dataset, server, DB version etc. the performance results were equivalent, or biased towards EXCEPT.
Can you give...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2010 at 9:53 am
Now, there's an idea. Thanks, Remi.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2010 at 9:45 am
Lynn Pettis (1/17/2010)
Jeff Moden (1/17/2010)
itsmeman (1/5/2010)
This issue is done for now....Two way street here... please explain how this issue is "done for now".
My guess, they ran the update that...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2010 at 9:43 am
Sorry about that... that's why I only store file names for images.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2010 at 9:43 pm
A self join with a ROW_NUMBER reference would probably do it. If you want a coded answer, please see the first link in my signature line below.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2010 at 9:40 pm
Ummmm... I tried to find xp_restore_filelistonly in my installation of 2k5 and it doesn't exist nor is it in Books Online.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2010 at 9:33 pm
Simon Facer (1/17/2010)
MS recommends that you dont have any SP content database over 100GB
I'd really like to see the link for that, please.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2010 at 9:27 pm
itsmeman (1/5/2010)
This issue is done for now....
Two way street here... please explain how this issue is "done for now".
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2010 at 9:26 pm
Viewing 15 posts - 40,231 through 40,245 (of 59,098 total)