sql server 2005 - Are there any advantages to use varchar over decimal for Price and Value -


I was debating against my suggestion to store value, value and other similar information with my friend.

Based on my view,

  1. Calculations will be difficult because we have to move back and forth.
  2. The integrity of the data will be lost.
  3. Poor performance of the index
  4. Sorting and aggregate functions will also require casting

and so on. e.t.c.

But he was saying that in his previous planning, all people used to store such values ​​in the context, because communication between DB and APP is very effective in this approach. (I still can not accept it)

Do you have some advantages in collecting such values?

Note: I 'is not talking about columns like Phone No, Id, ZIP Code, SSN etc. I know that Vorar is most suitable for those people. Columns are price based, and of course the calculations will be included in some way or the other.

none

Try looking back one value further and see how much data you lose.

  DECLARE @foo TABLE (once varchar (30)) INFER @foo VALUES 11.2222222222) INFER @fooVALUES (22.3333333333) INSERT @foo VALUES (33.1111111111) Select CAST (CAST (once AS Float) AS varchar (30)) from @foo  

I will also mention that currently employment operate differently ... he last < / Em> is no longer on employment ....


Comments

Popular posts from this blog

Eclipse CDT variable colors in editor -

AJAX doesn't send POST query -

wpf - Custom Message Box Advice -