Viewing 15 posts - 47,416 through 47,430 (of 59,095 total)
My second swag would be that, as you suggest, both will cause some sort of index scan.... but because the WHERE NOT IN has only 42.857% as many items to...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2008 at 8:22 pm
Yeah... my first swag would be that this might be a boondoggle... tell me which company in the world has 50 million employees as the op suggests. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2008 at 8:06 pm
Ah... understood. Then, you may not need a book at all... there're examples in Books Online.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2008 at 7:39 pm
Mike Levan (11/3/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2008 at 7:36 pm
Lynn Pettis (11/3/2008)
Jeff Moden (11/3/2008)
Sridevi (11/3/2008)
I wrote a function and i got the result too.
CREATE FUNCTION select_concat (@A INT )
RETURNS VARCHAR(MAX) AS BEGIN
...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2008 at 7:24 pm
Then you should probably split it up... doing an update on something that large all at once will probably drive your code past the "tipping point" that every server seems...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2008 at 7:20 pm
aevans1981 (11/4/2008)
I have read through most of this post, but not all, I am using the code that was originally supplied.
When I try fn_WorkDays(27/10/2008...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2008 at 7:16 pm
Heh... the best tip has already been given... did you get rid of the cursor?;)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2008 at 7:06 pm
Some will take exception to it, but my feeling is that if it will never me anything but a (-1), then hardcoding it makes it pretty clear when it comes...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2008 at 6:58 pm
Heh... thanks, Peter... I put that in my code but forgot to mention it.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2008 at 5:32 pm
sam (11/4/2008)
Thanks for the direction. I still am finding it difficult to understand how to do this. The deadline for this is today, is there anyway you...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2008 at 5:22 pm
I'd probably make a Clustered PK on Phone_ID.
I'd seriously question why User_ID is going to be stored as a VARCHAR(20) but believe it would also need an index.......
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2008 at 4:30 pm
Robert klimes (11/4/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2008 at 4:24 pm
Spot-on, David.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2008 at 4:14 pm
stax68 (11/4/2008)
Jeff Moden (11/4/2008)
Keep it clean, slick. 😉
Oh, I do - mens sana in corpore sano old chap.
And, don't blame me if you don't understand what I'm saying....
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2008 at 3:30 pm
Viewing 15 posts - 47,416 through 47,430 (of 59,095 total)