pksutha (3/22/2011)

---

My answer is like this
first part which is i 've answered:

Declare @value1 decimal(20,10),@value2 decimal(20,3)

SET @value1 = 1234567890.123456789
SET @value2 = 0.1

SELECT @value1 * @value2

Second part is screened answer:

DECLARE @value1 DECIMAL(20,10), @value2 DECIMAL(30,13)
SET @value1 = 1234567890.123456789
SET @value2 = 0.1

SELECT @value1 * @value2


Ans:
The screened answer is u 've declared value2 decimal(30,13)... why u need like that?
my answer is Declare @value1 decimal(20,10),@value2 decimal(20,3)...... this is enough in SQL server 2005

Duncan Pryde (3/21/2011)

---

Excellent explanation. Couldn't have put it better myself.

Duncan Pryde (3/22/2011)
That's kind of the "moral" of the question. Never use a "bigger" decimal/numeric than you actually need.

rlswisher (3/22/2011)

---

Declare @value1 numeric(38,10)
Declare @value2 numeric(1,1)
SET @value1 = 1234567890.123456789
SET @value2 = 0.1
SELECT @value1
SELECT @value2

SELECT @value1 * @value2
= "123456789.012345679"

Toreador (3/22/2011)

---

The moral I've drawn is that maybe Floats aren't as bad as we thought...