Viewing 15 posts - 53,866 through 53,880 (of 59,089 total)
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
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 <...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 3:00 pm
Interesting. Can you post the code that you used to perform your test?
Now, you sound like me 😀 and, dang it... ya beat me to it 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 2:49 pm
Outstanding, Edogg! Thank you for the feedback!
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 2:38 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 2:36 pm
This should do it...
UPDATE Grade
SET Grade_Name = CASE
WHEN Grade_ID = '35800'
THEN 'TRANSCOPY' + CHAR(153) --™
...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 2:33 pm
Not trying to be a smart guy here...
What did you learn by this?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 2:13 pm
Jpotucek (11/28/2007)
exec sp_helpdb comes...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 2:03 pm
That's easy... it would be the person with the most to loose if the design is bad 😉 That's the only way someone will be interested enough in doing...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 1:41 pm
Doug Stoltz (11/28/2007)
1) I belive my earlier statement about the 2 web users sharing the same connection are correct, but I believe...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 1:30 pm
oh, be careful with IDENT_Current... lot's of folks can insert rows in that very brief time span between the time you do an insert and the time you use IDENT_Current.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 12:59 pm
Sorry about the EM thing... still trying to flatten out a crease in my brain with coffee...
If you set the scripting options correctly in Query Analyzer, you can generate such...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 12:55 pm
Ron_Kunce (11/28/2007)
Thanks for the Ammo!:D
Heh... ammo is one thing... learning how to shoot it straight may be another. My advice is to play with the code I gave you......
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 12:50 pm
How do you pronounce this, i.e. what comes after trillion
Heh... "Quadrillion"...
Mill = 1
Bill (or BI) = 2
Tri = 3
Quad = 4
etc, etc...
Except in some European countries 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2007 at 12:40 pm
Viewing 15 posts - 53,866 through 53,880 (of 59,089 total)