Viewing 15 posts - 43,321 through 43,335 (of 59,063 total)
Jeffrey Williams (6/17/2009)
only4mithunc (6/17/2009)
since by default the unique identifire is non-clustured , the records should be in the same order I have inserted na..?
By definition, a table has no order....
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2009 at 11:53 am
Carl Federl (6/17/2009)
Just for discussion, how do you stop anyone from using tempdb ?
Do what any DBA does... setup a script to wait for the appropriate quiet time. 🙂
I've used...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2009 at 11:48 am
Rich96 (6/17/2009)
Jeff & Christopher.. thanks so much for the feedback! Looks like I have some reading to do.
You bet, Rich... thanks for the feedback.
By the way, what's in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2009 at 10:39 am
GilaMonster (6/17/2009)
Paul White (6/17/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2009 at 10:35 am
Paul White (6/17/2009)
Lynn Pettis (6/17/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2009 at 10:33 am
GilaMonster (6/17/2009)
Jeff Moden (6/16/2009)
Now, if we could just get them to say that UPDATEs always work in clustered index order... 😛
They won't. The unofficial word from one of the guys...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2009 at 10:26 am
Rich96 (6/17/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2009 at 10:23 am
I believe a function as a check constraint is going to slow down INSERTs quite a bit. Wouldn't it be better to setup a little DRI instead?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2009 at 8:57 am
To add to those comments.... I don't know how much performance is important for this task, but an old fashioned pre-aggregated CrossTab can be quite a bit faster than a...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2009 at 8:53 am
Jason Coleman (6/17/2009)
Right... finally started thinking straight...
selectactivity_date,
to_char(activity_date,'IW')-to_char(sysdate,'IW') as Date_diff
from
dw.calendar
and then hey presto! :w00t:
Outstanding. Thanks for the feedback on this, Jason.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2009 at 8:48 am
Jeff Moden (6/17/2009)
Carl Federl (6/17/2009)
There is also this note:
If tempdb...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2009 at 8:47 am
Carl Federl (6/17/2009)
There is also this note:
If tempdb is in...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2009 at 8:35 am
Rich96 (6/17/2009)
-JeffUnfortunately I'm dealing with a 3rd party vendor that could not process the normalized table. In fact I've had to convert all my alphanumeric fields to ASCII..
Heh... been...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2009 at 8:32 am
By the way... the code windows still don't work well with IE. I know a lot of development folks use FF, but the other half uses IE.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2009 at 10:58 pm
SQLTeam, Wrox, and a couple of other forums have a "#" button in the menu like, say, the parenthesis you have for the quote code in the current menu. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2009 at 9:05 pm
Viewing 15 posts - 43,321 through 43,335 (of 59,063 total)