In traditional rounding true but BR is not traditional rounding

Not true.

Did you read definition of BR?

It says if ALL following digits are zeros.

Problem is you don't know the ALL following...

David, there are no numbers "exactly half way" as BR specified.

Read previous page.

Pay attention to the part where I explain why it's not possible to have a value equal to...

Pray you'll be the only user forever.

Otherwise response time not gonna be that good.

And 100k rows is not a real life database size.

Remember, Excel can hold 65k rows.

And don't you...

Normalization is just the way of storing data.

If it's stored correctly from the beginning there is no need for conversion.

I did not time "de-normalization part" in your script either.

If you are not sure don't say.

Otherwise people would consider you don't know what you are talking about.

Should your "not sure" be considered as an apology?

It's not me.

It's math.

Good for you, you did not forget it completely, and I needed just remind you some important things.

Unfortunately, not everyone here is that lucky.

And what is more...

Yes, BR is defined differently, and its definition of BR is wrong.

It returns wrong results every time it's different from TR by definition.

So, what's the point to use BR if every time it is different from TR it's wrong?

Would it be more logical to use rounding which is right every time, even...

Sorry to remind you, but you still failed to answer the question:

Is there place for values 2/3, 1/9, 4/7 and, if yes, where is it?

> BR is used in...

Is it good or bad result?

Let's check:

SELECT StringValue,

CASE WHEN StringValue...

> You are always convinced that you are never wrong.

Are you sure you are right?

I can tell.

It's ordered to sort by some kind of group (integer value at the beginning) and then by item (second part).

And you cannot explain why to sort serial numbers...

By the way it requested to be ordered I can conclude it's 2 concatenated values.

Saving concatenated strings in tables is an error which will cause (already causes) problems in retrieving...

Then what did you do?

You split original column into 2 (normalized the data) and built derived table with normalized data on fly.

No indexes, no statistics.

Worst possible approach.

Populate @TestData with 100k...

What was the first post about?

I don't see any "quote delimited format" here.

Can you explain what exactly do you need?