Viewing 15 posts - 42,391 through 42,405 (of 59,067 total)
Heh... kewl. 🙂 In that case, I stand corrected.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2009 at 6:58 pm
Do you know of anything that you can use in SELECT/INTO that will create a float column that isn't specifically cast as a float?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2009 at 6:34 pm
Paul White (8/9/2009)
Jeff Moden (8/9/2009)
No need for rounding if you're going to cast the answer...
Hey Jeff,
Valid point, but let me explain myself: I left the ROUND in for two reasons:
1....
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2009 at 6:14 pm
Paul White (8/9/2009)
(@Beverley: Jeff is kidding)
Heh... not quite. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2009 at 6:12 pm
First of all, take a look at the article at the first link in my signature line at the bottom of this post. Then take a look at the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2009 at 6:01 pm
RichSmith (8/9/2009)
Can anyone help me get this to work as a recursive query in SQL Server 2000?
Nope... but I can show you the right way. 😉 Gimme a couple...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2009 at 4:47 pm
mesql (7/29/2009)
One is the the time dim and the hour dim
In the time dim I have timeid, fulldate (2000-01-05 00:00:00.000) month...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2009 at 4:43 pm
If you need all the columns from all 3 of the tables, I'm not sure you'll ever be able to make it as snappy as you'd like for a view......
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2009 at 4:34 pm
Heh... I like the last line of that conversation except that's normally where I break out the pork chops with the bone in them. 😛 Getting back to the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2009 at 4:25 pm
Thanks for the feedback. 5.4 million rows, eh? If the solution I posted takes longer than, ummm... 40 seconds or so, post back... there's a little trick we...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2009 at 2:33 pm
It doesn't necessarily help your current problem, I know you probably can't change it, and you may not even be concerned, but judging from the fact that you have more...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2009 at 2:12 pm
Heh... my response would have been the same 5 years ago. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2009 at 1:58 pm
Nica,
I almost forgot... my code assumes that the values that are in the CODE column are unique. If they are not, then we really need you to post data...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2009 at 1:54 pm
Sorry... almost forgot... I suspect that the indexing you have will suffice although a covering index on just the columns in the first copy to the working table would actually...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2009 at 1:49 pm
Heh... "The devil's in the data", I always say. Sorry I missed the thing on PLNO = 4. I didn't spend much time with your code other than...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2009 at 1:46 pm
Viewing 15 posts - 42,391 through 42,405 (of 59,067 total)