Thanks, Murali.

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...

It's not the disk... it's a chunk or two of code somewhere. Heh......

That's the real key... it shouldn't be. You've hit the nail on...

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.

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...

Heh... who cares about the precision... using FLOAT, you've lost some accuracy. Think not? Try this...

DECLARE @Radius FLOAT(53)

...

Perfect. Thanks for the feedback.

Just to be sure... you know what the "Tally" table is and how to build one?

Similar thing can be done in SQL Server...

SELECT Number AS CharNum, CHAR(Number) AS Character

FROM Master.dbo.spt_Values

WHERE Type = 'P'

AND Number <...

Now, you sound like me 😀 and, dang it... ya beat me to it 😛

Outstanding, Edogg! Thank you for the feedback!

By the way... your code seems to indicate that the Grade_ID is stored as a VARCHAR. If it's trully a numeric throughout, you may want consider changing the datatype...

This should do it...

UPDATE Grade

SET Grade_Name = CASE

WHEN Grade_ID = '35800'

THEN 'TRANSCOPY' + CHAR(153) --™

...

Not trying to be a smart guy here...

What did you learn by this?

Jpotucek (11/28/2007)

---

trying to come up with a few commands that I can use to query my SQL Server 2000 Instances and Document my Databases - preferably Excel

exec sp_helpdb comes...