Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • PowerCenter H2L
  • All Products

Table of Contents

Search

  1. Abstract
  2. Supported Versions
  3. How to Migrate Microsoft SQL Server Connections from the OLE DB to the ODBC Provider Type

How to Migrate Microsoft SQL Server Connections from the OLE DB to the ODBC Provider Type

How to Migrate Microsoft SQL Server Connections from the OLE DB to the ODBC Provider Type

Back Next

Are there data type support changes between the ODBC and OLE DB provider types?

Are there data type support changes between the ODBC and OLE DB provider types?

No. Both the ODBC and OLE DB provider types support the following data types:
Microsoft SQL Server Data Type
Range
Transformation Data Type
Range
Binary
1 to 8,000 bytes
Binary
1 to 104,857,600 bytes
bigint
- 9,223,372,036,854,775,808 to 9,223,372,036,854,775,807
bigint
-9,223,372,036,854,775,808 to 9,223,372,036,854,775,807
Precision 19, scale 0
Bit
1 bit
String
1 to 104,857,600 characters
Char
1 to 8,000 characters
String
1 to 104,857,600 characters
Datetime
Jan 1, 1753 A.D. to Dec 31, 9999 A.D.
Precision 23, scale 3
(precision to 3.33 milliseconds)
Date/Time
Jan 1, 0001 A.D. to Dec 31, 9999 A.D.
(precision to the nanosecond)
Datetime2
Jan 1, 0001 A.D. 00:00:00
to
Dec 31, 9999 A.D. 23:59:59.9999999
Timestamp
Precision 22 to 27
Decimal
Precision 1 to 38, scale 0 to 38
Decimal
PowerCenter: Precision 1 to 28, scale 0 to 28
Informatica Developer: For transformations that support precision up to 38 digits, the precision is 1 to 38 digits, and the scale is 0 to 38.
If you specify the precision greater than the maximum number of digits, the Data Integration Service converts decimal values to double in high precision mode.
Float
-1.79E+308 to 1.79E+308
Double
Precision 15
Image
1 to 2,147,483,647 bytes
Binary
1 to 104,857,600 bytes
Int
-2,147,483,648 to 2,147,483,647
Integer
-2,147,483,648 to 2,147,483,647
Precision 10, scale 0
Money
-922,337,203,685,477.5807 to
922,337,203,685,477.5807
Decimal
Precision 1 to 28, scale 0 to 28
nchar
1 to 4000 characters
String
1 to 104,857,600 characters
ntext
1 to 1,073,741,823 bytes
Text
1 to 104,857,600 characters
Numeric
Precision 1 to 38, scale 0 to 38
Decimal
PowerCenter: Precision 1 to 28, scale 0 to 28
Informatica Developer: For transformations that support precision up to 38 digits, the precision is 1 to 38 digits, and the scale is 0 to 38.
For transformations that support precision up to 28 digits, the precision is 1 to 28 digits, and the scale is 0 to 28.
If you specify the precision greater than the maximum number of digits, the Data Integration Service converts decimal values to double in high precision mode.
nvarchar
1 to 4000 characters
String
1 to 104,857,600 characters
Real
-3.40E+38 to 3.40E+38
Double
Precision 15
Smalldatetime
Jan 1, 1900, to June 6, 2079
Precision 19, scale 0
(precision to the minute)
Date/Time
Jan 1, 0001 A.D. to Dec 31, 9999 A.D. (precision to the nanosecond)
Smallint
-32,768 to 32,768
Integer
-2,147,483,648 to 2,147,483,647
Precision 10, scale 0
Smallmoney
-214,748.3648 to 214,748.3647
Decimal
Precision 1 to 28, scale 0 to 28
Sysname
1 to 128 characters
String
1 to 104,857,600 characters
Text
1 to 2,147,483,647 characters
Text
1 to 104,857,600 characters
Timestamp
8 bytes
Binary
1 to 104,857,600 bytes
Tinyint
0 to 255
Integer
-2,147,483,648 to 2,147,483,647
Precision 10, scale 0
Uniqueidentifier
Precision 38, scale 0
String
To successfully move or change Uniqueidentifier data, ensure that the data is in the following format:
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
where
x
 is a hexadecimal digit in the range 0-9 or a-f.
Varbinary
1 to 8,000 bytes
Binary
1 to 104,857,600 bytes
Varchar
1 to 8,000 characters
String
1 to 104,857,600 characters
The following table compares Microsoft SQL Server synonyms to PowerCenter transformation data types:
Synonym
Transformation
Binary Varying
Binary
Character
String
Character Varying
String
Dec
Decimal
Double Precision
Double
Integer
Integer

Uniqueidentifier Data Type

Uniqueidentifier is a Microsoft SQL Server data type that is used to store Globally Unique Identifiers (GUIDs). It can store 16 bytes of data.
PowerCenter imports the Microsoft SQL Server Uniqueidentifier data type as a Microsoft SQL Server Varchar data type of 38 characters.
The Developer tool treats the Uniqueidentifier data type as String. To move or change Uniqueidentifier data, connect the Uniqueidentifier column to a String column. To successfully move or change Uniqueidentifier data, ensure that the data is in the following format:
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
where
x
 is a hexadecimal digit in the range 0-9 or a-f.
For example,
6F9619FF-8B86-D011-B42D-00C04FC964FF
 is a valid Uniqueidentifier value.
The Developer tool can store 16 bytes of Uniqueidentifier data in 36 characters. However, since Uniqueidentifier data can be represented within two curly brackets, the Developer tool assigns two additional characters to the precision to accommodate the curly brackets. When you connect a Uniqueidentifier column to a String column, set the precision of the String column to 38 to successfully move or change Uniqueidentifier data.
0 COMMENTS
We’d like to hear from you!