Maybe.

Maybe not.

YOU DON'T KNOW BECAUSE YOU DON'T KNOW CONTEXT!

If the value has been rounded (does not matter in which way) that means you don't know what is the last digit....

Yes.

you're right.

0.66 could bring you to different assumptions depending on the situation it was generated.

Again, you don't know, because I didn't put it into context.

Brilliant!

Finally you've got it!

YOU DON'T...

SELECT ISNULL(S.PersonNum, T.PersonNum),

COUNT(S.ID - T.ID) as WorkedOnSchedule, -- if any one is NULL row will not be counted

COUNT S.ID as Scheduled,

COUNT T.ID as Worked

FROM dbo.AllMinutesInSchedule A -- table containing...

This will NEVER TRULY tell you how it's stored naturally, especially with Query Analyzer - as I have demonstrated.

Demonstrated where? Cannot see any demonstration.

I would have thought that the software/firmware/hardware...

Wow!!!

You should immediately report a bug in SQL Server (and all other computer systems)!

Because SQL Server reports that 2.0/3.0 = 0.666666

If 0.666666 = 0.6666660000000000000 then 2.0/3.0 > 0.666666

SQL Server returns...

Karma,

where do you see additional level of precision?

There are 6 precise digits, and they stay precise as no operation performed yet.

I said thay 7th, 8th and all following digits may...

> In the first case, 0.666666 reprepresents precisely 0.666666

What makes you think this is true?

And there is only one case:

0.666666

What value is represented by this decimal number?

One answer right for...

So, you admit

coming from the different sources same value 0.666666 could represent either 0.6666660 or 0.666666.

Or any another number between 0.666666(0) and 0.66666(9)

YOu don't have any reason to...

I catch every possible error inside my procedures using @@ERROR.

Your statement just is not true.

You are obviously doing something wrong.

Check your syntax.

Michael,

First you need to fix your comments.

Then I could take it into consideration.

2.0/3.0 is NOT naturally stored as 0.67

Run SELECT 2.0/3.0 and see how it's stored naturally.

Seeing that you can...

Mathematically:

if there is a number (one, single number) when it does not work - it does not work.

This is how it is.

To prove it works you need to prove there...

> Again, it is a decision based on what is known.

Known is that:

0.666666

0.045000

What is your assumption about following digits for the values represented by these numbers?

> one may assume that all further digits after the last 0 are also zero.

Based on what?

You know that assumption is wrong.

When SQL divides 2./3 and returns 0.666666...

It does not matter what it sees.

What seen thing means - what matters.

0.045000 represents actually supplied value 5/111.111 with 6 decimal digits precision.

So, result of BR function is wrong, because...

Do you understand word "precision"?

You've got 6 precise digits.

That's it.

This is the limit you can see.

Nobody can tell anything about any further digit.

Because they are UNKNOWN.

They are BEYOND GIVEN PRECISION.

You've...