Viewing 15 posts - 38,101 through 38,115 (of 59,072 total)
j-1064772 (6/1/2010)
Paul White NZ (5/5/2010)
Jeff Moden (5/5/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 1, 2010 at 12:09 pm
The lack of feedback on this post has me worried that the OP is actually using the alphabetic increment in the unfiltered mode. Please save your company a lawsuit...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 1, 2010 at 9:12 am
Nagesh S-432384 (5/31/2010)
changbluesky (5/31/2010)
---
create table mytable
(
potype varchar(10)
)
insert into mytable values
('AA'),
('BB'),
('CC')
declare @potypestring varchar(50)=''
declare @potype varchar(10)
declare mytype cursor local for
select potype from mytable
open mytype
fetch...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 31, 2010 at 8:49 pm
Well I'll be dipped. I guess I'm glad I didn't think of the "Difference between two row numbers" trick here. Without changing the number of rows in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 31, 2010 at 8:22 pm
BWAA-HAA!!!! I just realized the "Deep Dive" method is nothing more than the now old "difference between two sets of ROW_NUMBER()'s trick. Stupid me for not thinking of...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 31, 2010 at 7:45 pm
WayneS (5/31/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 31, 2010 at 7:39 pm
vijay.s (5/30/2010)
Paul White NZ (5/29/2010)
SELECT This.ClientCode,
This.FlowDate,
This.TempletID,
...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 31, 2010 at 6:18 pm
David.Poole (5/30/2010)
Even the best designed database system is going to crack under the pressure of that much data.
Heh... it hasn't yet. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
May 31, 2010 at 6:10 pm
Not to worry... I was going down the same path before I gave in to the lure of the Quirky Update.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 31, 2010 at 5:45 pm
You bet. Thanks for the feedback and thanks for listening. Gotta run, though... I've gotta call OSHA and tell them handrails won't be necessary. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
May 31, 2010 at 4:36 pm
Heh... dammit. I almost didn't post my solution for fear of just that. I really wanted to see a good self referencing solution.:pinch:
--Jeff Moden
Change is inevitable... Change for the better is not.
May 31, 2010 at 4:22 pm
Here's my take on the problem... sometimes ya just gotta cheat to keep it both simple and fast. 😛
declare @rangeTable table (start int, [end] int PRIMARY KEY CLUSTERED, MinStart...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 31, 2010 at 4:08 pm
I agree with Gail and I think that's the key to answering this question. What kind of clustering are you talking about?
I don't believe the original question you were...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 31, 2010 at 3:05 pm
Lynn Pettis (5/30/2010)
Though worded differently, this looks like a cross post. Please post any answers here.
I agree... same question. I have a possible answer and I'll post it...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 31, 2010 at 2:56 pm
all4miller (5/31/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 31, 2010 at 2:33 pm
Viewing 15 posts - 38,101 through 38,115 (of 59,072 total)