Viewing 15 posts - 40,651 through 40,665 (of 59,071 total)
Heh... ack! Serves me right for not reading the whole post before responding.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2009 at 9:38 pm
romah (12/14/2009)
I found the code in forum section to convert comma separated string to table
And I am...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2009 at 9:34 pm
In fact, Paul, you should write an article on this. Should be about as good a fight as the Running Total article. You'll drive the other MVP's absolutely...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2009 at 8:52 pm
Paul White (12/13/2009)
There is at least one case where the written order of the tables does matter.
Man... very, very well done. Thanks, Paul.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2009 at 8:48 pm
Heh... wow... Paul beat me to it and, for once, I'm glad so that I'm not the first to say something that most other people will disagree with. I...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2009 at 8:46 pm
Paul White (12/13/2009)
Steve Jones - Editor (12/13/2009)
Paul, that's interesting. I've not seen people writing joins as groups like you have. I think those parens are affecting things.
No parentheses version:
SELECT ...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2009 at 8:22 pm
I just can't resist helping someone who took the time to make it so easy for me to help. Well done on the original post.
This will do it. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2009 at 8:18 pm
Do you need accurate data for this or just a large amount of data to play with?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2009 at 8:09 pm
aaa-322853 (12/14/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2009 at 8:05 pm
I have to ask... what if someone needs a 4th WBS code?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2009 at 8:03 pm
I suppose you can trim down the WHERE clause in Paul's good code with the minor risk of finding things you didn't intend to...
WHERE
definition LIKE '%[0-9].[0-9].[0-9]%'...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2009 at 7:51 pm
First, the temporal clustered index you mention will help a lot. There's another trick associated with this type of "rolling delete" but I have a couple of questions, first.
1....
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2009 at 7:45 pm
To go along with what Bru said, if you want folks to give you a coded answer, please see the first link in my signature below to help you help...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2009 at 7:41 pm
Paul White (12/14/2009)
I don't think it set out to provide the most performant solution, just an interesting technique, which I guess it is.
Heh... true enough... almost like that whacko that...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2009 at 4:26 pm
Paul White (12/14/2009)
sam.walker (12/14/2009)
Paul White, I am certain this is not correct.
One of the longest threads ever on SSC was devoted to this: http://www.sqlservercentral.com/Forums/Topic695508-338-17.aspx
There is a handy summary of the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 14, 2009 at 3:19 pm
Viewing 15 posts - 40,651 through 40,665 (of 59,071 total)