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

Back Next

After I migrate to the ODBC provider type, what are the post-migration tasks that I must perform to retain the previous behavior with the OLE DB provider type?

The following table describes solutions for issues that you might encounter after you migrate to the ODBC provider type:

Issue	Resolution
PowerCenter sessions write data of the Bit data type as 1 and 0 to Microsoft SQL Server targets.	Set the value of the ProcesSQLServerBITASVarchar custom property to Yes to write the Bit data as T and F instead of 1 and 0.
PowerCenter sessions that write data of the BIT data type to Microsoft SQL Server targets fail if all of the following conditions are true: You configure the Microsoft SQL Server connection to use the ODBC provider type. You configure the data movement mode for the PowerCenter Integration Service as ASCII. You configure the value of the custom property ProcesSQLServerBITASVarchar as Yes.	Set the value of the ProcesSQLServerBITASVarchar custom property to No or set the data movement mode to Unicode .
PowerCenter sessions that write data of the Smalldatetime data type to Microsoft SQL Server targets fail with a data overflow error.	Set the value of the SQLServerLegacySmallDateTime custom property to Yes .
PowerCenter sessions that write data of the Date data type to Microsoft SQL Server targets fail.	Set the value of the SQLServerBulkSupportDateFormat custom property to YYYYMMDD to support the MM/DD/YYYY and YYYYMMDD date formats.