Viewing 15 posts - 32,911 through 32,925 (of 59,102 total)
Paul Herbert (8/10/2011)
A minor correction if you don't mind. If you are going to quote my 'Really?!", I think it needs both...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2011 at 6:28 pm
Gosh... I wouldn't use CHECKSUM for such a thing. It's nothing but a simple Exclusive OR and getting duplicate CHECKSUM values for different data is much more likely than...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2011 at 6:14 pm
Hear here! This editorial should be required reading for anyone involved with data especially the managers that want the data turned into information. Well done, Steve!
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2011 at 6:00 pm
Mark-101232 (8/10/2011)
SELECT t.ID,
DATEADD(wk,n.N-1,t.StartDate) AS NewStartDate
FROM #MyCrazyDateThing t
INNER JOIN dbo.Tally n ON n.N BETWEEN 1 AND LEN(t.WeekPattern)
...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2011 at 3:33 pm
No need to fuss with all that. Just do a BCP out to the file with no row terminator. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2011 at 3:29 pm
If you don't care to track what the dupes are, just put a UNIQUE index on the columns with the IGNORE DUPES option and do the inserts.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2011 at 3:27 pm
My recommendation would be to skip the HierarchyID and go straight to "Nested Sets" which Joe Celko made famous.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2011 at 3:23 pm
Kenney Hill (8/10/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 10, 2011 at 11:09 am
Dugi (8/9/2011)
Jeff,Thanks for the very nice stuff! Simple to say that I need to read it again and doing more and more practicing and practicing ...!
Have a nice day,
Dugi
Hi Dugi,
Long...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2011 at 8:45 pm
Mattrick (8/9/2011)
Thanks for the article and the performance metrics. After having read it, I will be sending a link to all of the developers in my department as a...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2011 at 8:41 pm
Revenant (8/9/2011)
JeffI have printed this article and put it into my 'keep for frequent reference' folder.
Much thanks!
You bet, Revenant. Thank you for the read and the feedback. 🙂 ...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2011 at 8:37 pm
ChrisM@Work (8/9/2011)
Crackin' good read as always Jeff.
Thanks, Chris. Always good to hear from you.
I never noticed it before. Your signature line says you're a defender of moggies. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2011 at 8:34 pm
John Dempsey (8/9/2011)
Long time no see, John. Thanks for the feedback. Heh... I'd forgotten about the "Pork Chop Logo". I wonder how T-Shirts with it would sell...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2011 at 8:23 pm
tfifield (8/9/2011)
It really puts the kabosh on the rCTE method. It also shows something that I found a while back. That the old fashioned tally table...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2011 at 8:19 pm
lstrashnoy (8/9/2011)
WITH --===== Itzik-Style CROSS JOIN counts from 1 to the number of days needed
E1(N) AS (
...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2011 at 8:04 pm
Viewing 15 posts - 32,911 through 32,925 (of 59,102 total)