I am importing a table from a mySQL Database. The Database Column is defined
as a numeric(6,2). I am receiving an error the the column is too wide for the
import, the only value I can see in 18 rows (small table) is 22500.00. I have
tried changing the size where I can, it doesn't seem to work. This seems like
a legal numeric, other columns with the same data, i.e. 124000.00 and
numeric(6,2) seem to work fine, any clue as to what is happening on this.
Currently I am ignoring the column on the import as work-around but this is
not the best solution obviously.

Hello carolus.holman,

Which column is defined as DECIMAL(6,2)?

Try this is QA?

select cast(22500.00 as decimal(6,2))



Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

Well this is part of an SSIS Package, the program won't let me modify the
output. Looking at the mySQL server everything seems normal. No funky
characters coming through, when I export to CSV it looks fine. I have seen on
this board where someone disabled Fast Table load, but that didn't work for
me.

mySQL tbale the column is defined as numeric(6,2)

On the SQL2005 side when I worte the script it was also defined as a
numeric(6,2).
Interestingly enough typing 22500.00 into the column on SQL2005 when it was
defined as numeric(6,2) caused an error. So is numeric(6,2) only good to
9999.99? My understanding is it is 6 digits with 2 decimal places. 999999.99?
Am I wrong on this? Shoud I use a decimal instead?

"Allan Mitchell" wrote:

Hello carolus.holman,


Have a look at this topic in BOL then if you are using 2K5

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/9d862a90-e6b7-4692-8605-92358dccccdf.htm


Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

Hello carolus.holman,


Have a look at this topic in BOL then if you are using 2K5

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/9d862a90-e6b7-4692-8605-92358dccccdf.htm


Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

Yes I saw this. A number like 22500.00 should fit in the numeric(6,2) data
type. but it doesn't. What is strange is the defintion seems to be 6 TOTAL
digits including the precision. Can this be correct? e.g. 1234.56 =
numeric(6,2).

I changed it to Numeric(6,0). I could then type 123456, apon typing
123456.99 it rounded it to 123457.

Is this the expected usage? I cannot trust the mySQL to be correct, however
it doesn't seem to be correct using microsoft own reference.



"Allan Mitchell" wrote:

Yes I saw this. A number like 22500.00 should fit in the numeric(6,2) data
type. but it doesn't. What is strange is the defintion seems to be 6 TOTAL
digits including the precision. Can this be correct? e.g. 1234.56 =
numeric(6,2).

I changed it to Numeric(6,0). I could then type 123456, apon typing
123456.99 it rounded it to 123457.

Is this the expected usage? I cannot trust the mySQL to be correct, however
it doesn't seem to be correct using microsoft own reference.


"Allan Mitchell" wrote:

So in the end I finally figured out that it is not as I thought. I think the
BOL should be more clear, somehting like numeric(6,2) is the same as 9999.99.
Or Numberic(10,2) is the same as 12345678.90. Not all of us a technical
wunderkinds dealing with byte counts, I have voiced this to MS in the past, a
picture is worth a thousand words, which is what I have spent on this stuff!

"carolus.holman" wrote: