Viewing 15 posts - 43,906 through 43,920 (of 59,063 total)
Florian Reischl (5/2/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 8:39 pm
Heh... I'd recommend that you may need to actually put some data in the table before you even think of trying to optimize a query.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 8:37 pm
dave b (5/2/2009)
BTW...I just started reading your post about the "Tally" table.
I am now officially on a quest to eliminate my cursors and...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 8:27 pm
Heh... it could simply be that the non-Ansi join was returning the incorrect row count to begin with. From BOL...
In earlier versions of Microsoft® SQL Server™ 2000, left and...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 8:22 pm
I agree. It would be real handy to click on Topic Options and be able to select "Unsubscribe from this topic only".
Of course, it would also be nice if...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 8:07 pm
Your criteria is wrong. You shouldn't add minimum to the total and the price because in cases there there is anything >0, it will always exceed the minimum which...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 7:48 pm
Paul White (5/2/2009)
...as I say, it's a shame about the compilation time.
Heh... yeah, I agree... for a million rows, it's a shame. For more common numbers like 8000, all...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 7:01 pm
Paul White (5/2/2009)
Jeff Moden (5/2/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 5:56 pm
Paul White (5/2/2009)
Well spotted! I must admit I looked at it and gave up after a few minutes...I guess replacing LEN with DATALENGTH might fix it up too?
Paul
Yes... but...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 5:36 pm
george sibbald (5/2/2009)
that would upset the heck out of most auditors unfortunately.
Why? I would think that the lack of security setup by the DBA that allowed it's misuse would...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 5:11 pm
Phil Factor (5/2/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 5:00 pm
For the most part, if you have defined a linked server, there is usually no need at all for OPENQUERY or anything like it. Just use a 4 part...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 1:27 pm
Heh... I'm definitely NOT an ANSI purest and I definitely DON'T believe in the myth of portable code especially when it comes to high performance batch code.
For all the advantage...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 1:03 pm
george sibbald (5/2/2009)
as part of the same job enable xp_cmdshell just before the bcp and disable it again immediately afterwards
That would certainly work... I guess my question would be...
If...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 12:43 pm
troy.hodge (5/1/2009)
I want to confirm that is infact correct and a good Idea. Are their short comings to this approach? Any reason we would not want to do this?
Some of...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 2, 2009 at 12:21 pm
Viewing 15 posts - 43,906 through 43,920 (of 59,063 total)