Hi.

I am trying to run a simple SQL Server 2005 Integration Services package
against
a single Oracle database table.
The table has several columns having datatype NUMBER without any precision.

When trying to open the Columns tab in the OLE DB Source Editor I get an
error telling me that the output column has a precision that is not valid.
In other words, the precision has to be between 1 and 38, while the actual
precision
in Oracle is 0.

Anyone have any workarounds for this ?
(Beyond making a copy of the table in Oracle with some precision defined for
the difficult columns)

Kind Regards,
Torkild Hagen

Not sure if this is beyond, but you could try creating a view on top of the
fact table and then using the CAST function on the column which I think is
ANSI SQL so should work on anything

e.g.

CREATE OR REPLACE VIEW OLAP_VIEW
(OLAP)
AS
SELECT CAST(1 as NUMBER(20,5)) "OLAP" FROM dual

Hi Ian,

and thanks for the swift response.

I tried your solution. It failed but gave me an idea.
I typecasted to VARCHAR2 instead, and then let SSIS implicitly cast it back on
the way into SQL Server 2005. This works like a charm

Once again, thanks a bunch !



"Ian Goodchild" wrote: