Viewing 15 posts - 55,681 through 55,695 (of 59,072 total)
Like I said on the other forum, I think you have a bit of a technical error in the code. I think this...
ImportFullPath = ImportPath & ImportFile
... should be this...
ImportFullPath...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2007 at 11:12 pm
This is what I call "RBAR" (pronounced "ree-bar" and is a "Modenism" for "Row by Agonizing Row") because you have variables on the right side of an update. The only...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2007 at 11:10 pm
Thank you for the detailed explanation... I have just a couple more questions , if you don't mind...
Can you post the table of results for the "A" items?
In the formula 18(18)+18(18-15), do...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2007 at 9:52 pm
Very nicely stated and explained, Steve.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2007 at 9:40 pm
Thanks Wutang
, but, nope... just a regular ol' SQL guy answering questions if I can. ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2007 at 6:08 pm
Have you tried anything on your own?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2007 at 10:31 pm
Now, there's a lesson learned... Thanks, Serqiy.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2007 at 9:43 pm
No effect... maybe size of TempDB? Mine is set to 1 gig...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2007 at 3:51 pm
Ok... replaced the CROSS JOIN with INNER JOIN like it was supposed to be...
DELETE AD1
FROM DBO.AILMENTDETAIL AS AD1
INNER JOIN DBO.AILMENTDETAIL AS AD2
ON AD1.AILMENTID = AD2.AILMENTID
...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2007 at 2:16 pm
That's what I get for answering email before the necessary amount of coffee... ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2007 at 2:05 pm
Heh... I don't think performance is the "black art" that so many think and, I agree... sometimes new hardware and SQL Server upgrades just don't do a thing...
3 years ago,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2007 at 12:30 pm
Dang... I gotta get 2k5... ![]()
Heh, I noticed the Peter converted the code to the good'n'proper ANSI style joins so that it's apparent that...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2007 at 9:58 am
It was a funny comment, indeed.
No, we're not make fun of anyone except for each other
But, I was serious about needing to...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 21, 2007 at 6:24 pm
Now, THAT's funny! ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 21, 2007 at 11:03 am
Perfect...
Obviously, you need to test this on a copy of the table before you try it on the real table...
DELETE ad1
FROM dbo.AilmentDetail_Test ad1,
dbo.AilmentDetail_Test ad2
WHERE ad1.AilmentID ...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 21, 2007 at 11:01 am
Viewing 15 posts - 55,681 through 55,695 (of 59,072 total)