# how do I convert a hex to a floating point number

 0 How do I convert a hex to a floating point number? as in 0x43F8E354 should be 497.776 This is SQL Server 2008 R2 I've tried [http://www.novicksoftware.com/UDFofWeek/Vol1/T-SQL-UDF-Volume-1-Number-23-fn_replinttobitstring.htm][1], but it does not look as if fn_replinttobitstring exists in Sql Server 2008 R2. In SSIS I can do like this: ``````Public Function ReadDouble(ByVal blobdata As Byte()) As Double ' Convert gain Dim MemoryStream As New System.IO.MemoryStream(blobdata) Dim BinaryReader As New System.IO.BinaryReader(MemoryStream) ReadDouble = BinaryReader.ReadDouble() End Function `````` But how to do this in T-SQL? [1]: http://www.novicksoftware.com/UDFofWeek/Vol1/T-SQL-UDF-Volume-1-Number-23-fn_replinttobitstring.htm more ▼ asked Jul 13, 2011 at 04:03 AM in Default Henrik Staun Poulsen 579 ● 13 ● 15 ● 16 @Henrik Staun Poulsen The function you have in your question does not do what you need even in SSIS because it converts the input to long integer not the floating point number. As @bopeavy already stated in the answer below, conversion to/from int (or bigint) from/to hex is already available in T-SQL. The only problem is that the statementselect convert(bigint, 0x43F8E354)returns 1140384596 not the desired 497.77600098Since your input is 4 bytes, 497.77600098 is not an accurate representation of the input. When you declare a variable as float then float(53) is assumed and 8 bytes of storage are needed. If your input is 4 bytes then your output cannot be a default float but is rather a single floating point number, which translates in T-SQL to float(24) and is sometimes called real. This one needs only 4 bytes of storage but the number of significant digits is only 7, so 497.77600098 does not comply with this limitation. Here is the sample showing that default definition of float needs 8 bytes of storage: ```declare @f float = 0.0; select datalength(@f); -- the above returns 8```Please confirm that you need a conversion to float(24) Jul 13, 2011 at 07:38 AM Oleg The number 497.76600098 is taken from another tool for which I do not have the source. But I can see that it converts the number to a FLOAT, not a REAL.I had shown the wrong function. That should be fixed now. Jul 14, 2011 at 12:11 AM Henrik Staun Poulsen @Henrik Staun Poulsen I added some comments to my answer related to your SSIS function. I hope they make sense. Jul 14, 2011 at 08:39 AM Oleg add new comment (comments are locked) 10|1200 characters needed characters left ▼ Viewable by all users

 0 There is a great discussion of this topic on the main SSC site which includes Jeff Moden, Peter Larsson (whom we know as @Peso on this site) and Martin Wills. Here is the link: http://www.sqlservercentral.com/Forums/Topic356756-8-1.aspx. I just tried the version which Martin Wills posted on page 3 which was in turn a recoding of Peter's code. Here is the paste from the post referenced above: ``````/* Hats off to Peter Larsson and Martin Wills for this one */ CREATE FUNCTION dbo.fnBinaryReal2Real ( @BinaryFloat BINARY(4) ) RETURNS REAL AS BEGIN DECLARE @Mantissa REAL, @Exponent SMALLINT, @IntValue INT, @Real2 REAL SELECT @Real2 = CAST(2.0 AS REAL), @IntValue = CAST(@BinaryFloat AS INT), @Exponent = (@IntValue & 0x7f800000) / 0x00800000, @Mantissa = 1.0 + (@IntValue & 0x007FFFFF) * POWER(@Real2, -23) RETURN SIGN(@IntValue) * @Mantissa * POWER(@Real2, @Exponent - 127) END GO ``````Here is the test: ``````declare @input binary(4) = 0x43F8E354; select dbo.fnBinaryReal2Real(@input) result; result ------------- 497.776 ``````Please note that the desired number 497.77600098 is not real (in both senses) because it has way too many digits for a real (a.k.a. float(24)) number to afford. However, if the accurate binary representation 0x43F8E354 of the single floating point number 497.776 is sufficient then the function above should help.Oleg more ▼ answered Jul 13, 2011 at 08:15 AM Oleg 15.9k ● 2 ● 4 ● 24 Hi Oleg,That is two very useful links.The first link to a function that solves my problem 300%. 100% to be able to decode the value, 100% for something that is fast, and 100% for beeing convertable to a view.The second link to 26 pages of excellent code. Whoa. You've made my day. Thank you very much.Best regards, Henrik Jul 14, 2011 at 12:21 AM Henrik Staun Poulsen Hi Oleg,Bummer, so that is what has been taking our server down... Well, we've noticed a memory leak, but it was so small it did not matter (much (on a 512 GB machine)).I'll fix that in 3 weeks time, when I'm back from summerholidays.Again, Thank you very much for your help.Best regards, Henrik Jul 14, 2011 at 12:10 PM Henrik Staun Poulsen add new comment (comments are locked) 10|1200 characters needed characters left ▼ Viewable by all users
 0 This would be a good place for you to start: [Convert Hex to int][1]. [1]: http://stackoverflow.com/questions/703019/sql-query-convert-integer-to-hex-and-hex-to-integer more ▼ answered Jul 13, 2011 at 04:30 AM bopeavy 146 ● 1 ● 1 ● 3 yes, I was able to find that link, but not get any use of it. Jul 14, 2011 at 12:06 AM Henrik Staun Poulsen add new comment (comments are locked) 10|1200 characters needed characters left ▼ Viewable by all users

### New code box

There's a new way to format code on the site - the red speech bubble logo will automatically format T-SQL for you. The original code box is still there for XML, etc. More details here.

By Email:

Need long-form SQL discussion? SQLserverCentral.com is the place.

Topics:

x1850
x991
x595
x2

asked: Jul 13, 2011 at 04:03 AM

Seen: 3836 times

Last Updated: Jul 14, 2011 at 12:03 AM