Understanding How Bulk Copy Converts Data Types
Concept Procedure

During copying, Bulk Copy retains the same data type when possible but performs a conversion if needed. For example, if you are copying data from a source that uses a Boolean data type and that data type is not available in the target, Bulk Copy converts the data to byte values, if available. If byte is not available, Int16 is used, and so on. The following table illustrates how conversion is performed (for each source data type, Bulk Copy tries to create target data type 1, but if that is not possible it tries data type 2, and so on):

Source data type Target data type 1 Target data type 2 Target data type 3 Target data type 4
Boolean Byte Int16 Int32 Int64
Byte Int16 Int32 Int64  
Int16 Int32 Int64    
Int32 Int64      
Int64 Int32      
Decimal Double Single    
Single Double Decimal    
Double Decimal Single    

The following FDO providers support the following data types:

  Oracle ArcSDE MySQL ODBC SDF SHP WFS SQL Server and SQL Server Spatial
Boolean Y   Y Y Y Y Y Y
Byte Y   Y Y Y   Y Y
Date/Time Y Y Y Y Y Y Y Y
Int16 Y Y Y Y Y   Y Y
Int32 Y Y Y Y Y Y Y Y
Int64 Y   Y Y Y   Y Y
Decimal Y   Y Y Y Y Y Y
Single Y Y Y Y Y   Y Y
Double Y Y Y Y Y   Y Y
String Y Y Y Y Y Y Y Y

Bulk Copy copies geometry properties as is, except that it will convert an arc to line segments if the destination does not support arcs.

Bulk Copy uses the following rules when copying an auto-generated identifier from the source feature source:

See Also