Viewing 15 posts - 40,426 through 40,440 (of 59,098 total)
AndrewSQLDBA (12/30/2009)
That is just bad news waiting to happen.
Heh... that's funny... I was just going to say the same thing about using SSIS. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2009 at 11:55 am
It depends... is the ToBase64String function something that you wrote or not? If it is, post it and someone may be able to come up something.
As an alternative, you...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2009 at 11:53 am
Justin James (12/29/2009)
There is not. I was thinking of using ROW_NUMBER(), but was unsure how to partition by each block of 6 rows.
I see you've already got that... simple integer...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2009 at 11:47 am
Justin James (12/29/2009)
Please see my original post for code to copy/paste.
Tell ya what, Justin... please see the first link in my signature line below. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2009 at 11:45 am
Auto update of stats being on is no guarantee that stats will be updated. IIRC, something like 20% of the table needs to be modified or new before an...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2009 at 11:38 am
Yep... not a misprint.
What was worse was when I tried to add a clustered index. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2009 at 11:22 am
No one mentioned things like the upgraded and properly working SQL Code windows on this sight. Posting and copying code was a real PITA for quite a while but...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2009 at 10:15 am
You may be causing massive page splits on the clustered index and massive extent splits on the non-clustered indexes if they are not in the same "order" as the data...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2009 at 9:43 am
corey_nunnery (12/29/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2009 at 9:29 am
To answer for Dave, yes... there are a couple of reasons but the big one is "accuracy". Using BETWEEN includes both end points and if time is ever induced...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2009 at 9:20 am
tm3 (12/30/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2009 at 9:17 am
Jack Corbett (12/30/2009)
Are there any triggers?
Spot on... another problem may be an explicitly declared transaction where all this stuff get's stacked up in the log and then get's "released" when...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2009 at 9:08 am
Heh... to wit... the bumble bee doesn't know that it's wings are too small and it's body is too heavy to fly.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2009 at 8:09 am
Posers (heh... I hate them and the moroffs that allowed them through the interview).
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2009 at 8:00 am
karthikeyan-444867 (12/28/2009)
1) If any date is misssing in the sequence then i don't want to calculate 'running total' after that row. But i can do the calculation...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2009 at 7:57 am
Viewing 15 posts - 40,426 through 40,440 (of 59,098 total)