Guess what? I have your same name. I know big whoop. But it is kind of cool writing to someone who has the same name – for me anyway.

Also I’m a Systems Administrator. I don’t think I’m quite as savvy with computers as you seem to be but nevertheless, I’m in the same field!! Wonder if we are related some distant way.

Possible but then the name Arbour is like Smith in Canada. Pages and pages of Arbour’s. Great, Great, Great Grandpa was a busy man!

Take care
Stephen

Here’s my results with blog-friendly formatting. Look closely at the last 2 lines:

select @res

123.123456789

—————————–
select CAST(@res as float(8))

123.1235

——————–
select CONVERT(FLOAT, @res)

123.123456789

————-
select ROUND(@res,8)

123.12345679

——————————–
select CONVERT(varchar, ROUND(@res, 8))

123.123

See how the result of taking a value of 123.12345679 turned into 123.123 the moment we converted it into a string? What the heck happened to the rest of the significant digits (i.e., where’s the 45679 part)? The same problem occurs if you use Cast() instead of Convert() to render the value in any string datatype.

Note that I was using MS SQL 2005, and this may be fixed with SQL Server 2008. I haven’t checked that yet.