importing data from Oracle - Is there a limitations on the datatypes that can be retrieved?

7 Apr 2006 2:31 PM

J. Adeli

Thanks,

J

7 Apr 2006 2:57 PM

Mike Labosh

> Thanks,

Hard to answer a question that doesn't have more information, but YES there
are limits:

SQL Server can store 8-, 16- and 32-bit integers in a TINYINT, (Short int?)
INT-type column. Other forms of numeric data types (What Oracle calls
Number(x, y) or Numeric(x, y) or whatever it is...) can be stored in SQL
Server as float or decimal.

Dates can be stored. Ditto, on currency types.

Character data that contains text strings can be stored in SQL Server as
CHAR, VARCHAR, NCHAR, NVARCHAR, TEXT, NTEXT, or, if pain is something that
you enjoy -- Binary, or VarBinary.

SQL Server also has an IDENTITY type that sort-of fits with whatever Oracle
calls a number-generator-function -- that thing that auto-generates
surrogate keys.

What did you actually have in mind to do?

--

Peace & happy computing,

Mike Labosh, MCSD MCT
Owner, vbSensei.Com

"Escriba coda ergo sum." -- vbSensei

7 Apr 2006 3:55 PM

J. Adeli

Thanks for the info. Need to import to MSSQL from different data source. I
found more info:
Supported data types
The .NET Managed Provider for Oracle supports the Oracle 8i-specific data
types such as CLOB, BLOB, NCLOB, and Bfile. The .NET Managed Provider for
Oracle 2.0 does not support the Oracle 9i XML data type or the Oracle 10g
data types Binary Float and Binary Double. (from
http://support.microsoft.com/kb/322158/en-us)

Show quote

"Mike Labosh" <mlabosh_at_hotmail.com> wrote in message
news:%23OKLbOlWGHA.4484@TK2MSFTNGP02.phx.gbl...
> > Thanks,
>
> Hard to answer a question that doesn't have more information, but YES
there
> are limits:
>
> SQL Server can store 8-, 16- and 32-bit integers in a TINYINT, (Short
int?)
> INT-type column. Other forms of numeric data types (What Oracle calls
> Number(x, y) or Numeric(x, y) or whatever it is...) can be stored in SQL
> Server as float or decimal.
>
> Dates can be stored. Ditto, on currency types.
>
> Character data that contains text strings can be stored in SQL Server as
> CHAR, VARCHAR, NCHAR, NVARCHAR, TEXT, NTEXT, or, if pain is something that
> you enjoy -- Binary, or VarBinary.
>
> SQL Server also has an IDENTITY type that sort-of fits with whatever
Oracle
> calls a number-generator-function -- that thing that auto-generates
> surrogate keys.
>
> What did you actually have in mind to do?
> --
>
>
> Peace & happy computing,
>
> Mike Labosh, MCSD MCT
> Owner, vbSensei.Com
>
> "Escriba coda ergo sum." -- vbSensei
>
>