Viewing 15 posts - 53,836 through 53,850 (of 59,072 total)
Heh... I'm a bit more like Clive... write my own tools whenever possible... that way, they do exactly what I want and I can change them if I need to.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2007 at 11:46 am
hey jeff...
Can you post the link of the forum u mentioned about ?
SQLServerCentral.com 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2007 at 11:40 am
Lynn Pettis (11/29/2007)
It could just be me, but the world is full of acronyms especially TLA's. What is CDR? Not the code, the acronym.
Heh... sorry Lynn... you're right...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2007 at 8:54 am
Thanks, Ed... and I fully understand about the "company name" thing... I gave almost the same answer on a similar request for code. Nice to see some "ethics".
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2007 at 8:45 am
Yep, I understand that... I think we're both talking about the same thing... just a different way...
I didn't say it quite right when I spoke of "accuracy" and I appologize......
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2007 at 8:36 am
EdVassie (11/29/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2007 at 8:19 am
Trying to figure out what you need and this seems simple to you because you know what you want... but we don't...
You say the copy/paste into Excel is tedious... what...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2007 at 8:10 am
Thanks, Murali.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2007 at 7:41 am
No, no... not that, Serqiy... I understand that.
I meant this type of accuracy when I said you better know what you're doing...
CREATE TABLE #Test(MyFloat FLOAT(53), MyDecimal DECIMAL(38,37))
INSERT INTO...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 10:15 pm
At occasional peroids we seem to suffer a very high number of SQL Deadlocks and performance issues.
It's not the disk... it's a chunk or two of code somewhere. Heh......
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 9:13 pm
I guess my thought would be - why does it have to be just ONE person's issue?
That's the real key... it shouldn't be. You've hit the nail on...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 9:01 pm
Heh... your welcome...
spt_values table is the "original" Tally table... it goes from 0 to 255 in 2k and I think it goes to 1023 or 1024 in 2k5.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 8:58 pm
A wise friend of mine once said, "A single test is worth a thousand calculations and speculations". Another wise friend of mine said, "A Developer must not guess... a...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 8:50 pm
The conversion caused the radius value to lose precision:
Heh... who cares about the precision... using FLOAT, you've lost some accuracy. Think not? Try this...
DECLARE @Radius FLOAT(53)
...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 6:47 pm
Perfect. Thanks for the feedback.
Just to be sure... you know what the "Tally" table is and how to build one?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 3:05 pm
Viewing 15 posts - 53,836 through 53,850 (of 59,072 total)