Eugene Elutin (7/29/2013) Jeff Moden (7/29/2013) Eugene Elutin (7/29/2013)
[b]Solomon Rutzky (7/27/2013)23847234872893475983479583749583749573945739 is all digits, is a valid number, but is NOT convertible to any SQL Server number types as it is larger than 38 digits
You can convert it to float (with lose of some precision ;-))
select cast('23847234872893475983479583749583749573945739' as float)
Considering that FLOAT only has 15 digits of precision, it'll be a pretty big loss. :-)
I wouldn't call 1.32% a such "big loss"
However you are right! It does depend! If this loss constitutes my interest in £ - I would probably die from heart-attack :-D
Heh... absolutely agreed but wasn't talking about the loss in "value" of the number. Was talking about the number of digits that would be lost when trying to determine if a long string could be checked for "IsAllDigits".
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs