The DataDirect Connect for ADO.NET data providers include provider-specific classes to support DataDirect Bulk Load. See
“Provider-specific Classes” for more information. If you use the Common Programming Model, you can use the classes in the DataDirect Common Assembly (see
“DataDirect Common Assembly”).
The DDTek.Data.Common assembly provides features that apply to all of the DataDirect Connect for ADO.NET data providers. In this release, the Common assembly includes classes that support DataDirect Bulk Load, such as the CsvDataReader and CsvDataWriter classes that provide functionality between bulk data formats.
See “DataDirect Classes” for more information on the classes supported by the DDTek.Data.Common assembly.
Figure 3-4 shows an ODBC environment copying data to an ADO.NET database server.
Bulk load operations between dissimilar data stores are accomplished by persisting the results of the query in a comma-separated value (CSV) format file, a bulk load data file. The file can be used between any DataDirect Connect for ADO.NET data providers that support bulk load. In addition, the bulk load data file can be used with any DataDirect Connect product that supports the bulk load functionality. For example, the CSV file generated by a DataDirect Connect
for ADO.NET data provider can be used by a DataDirect Connect
for ODBC driver that supports bulk load.
See “Sample Bulk Data Configuration File” for a more complex example of a bulk format data configuration file.
For the DataDirect Connect for ADO.NET data providers, the default source character data, that is, the output from the CsvDataReader and the input to the CsvDataWriter, is in Unicode (UTF-16) format. The source character data is always transliterated to the code page of the CSV file. If the threshold is exceeded and data is written to the external overflow file, the source character data is transliterated to the code page specified by the externalfilecodepage attribute defined in the bulk configuration XML schema (see
“XML Schema Definition for a Bulk Data Configuration File”). If the configuration file does not define a value for externalfilecodepage, the CSV file code page is used.To avoid unnecessary transliteration, it's best for the CSV and external file character data to be stored in Unicode (UTF-16).
The filename contains the CSV filename and a ".lob" extension (for example, CSV_filename_nnnnnn.lob). These files exist in the same location as the CSV file. Increments start at _000001.lob.