Table of Contents

Search

  1. About the Data Vault Administrator Guide
  2. Introduction to the Data Vault
  3. Data Vault Service Startup and Shutdown
  4. Data Vault Configuration
  5. Data Vault SSL Setup
  6. Data Vault ODBC Setup
  7. Data Vault Administration
  8. Data Repartitioning
  9. Partial Data Vault Copy
  10. Archived Data Migration
  11. Bulk File Uploader
  12. Data Vault Administration Tool
  13. Data Vault Logs
  14. User Account Privileges
  15. ssasql Command Line Program
  16. Data Vault Audit Log
  17. Sample Configuration Files

Data Vault Administrator Guide

Data Vault Administrator Guide

Source Data Flat Files

Source Data Flat Files

Before you run the bulk file uploader, save the flat files that contain the source data to a directory accessible to Data Vault. When you are ready to run the uploader, create a signal file in the same directory.
The source data flat files can have any extension. The rows can have any string as the row or column delimiter, as long as the delimiter is supported by Data Vault. The number of rows in each flat file file must be less than 2 billion.
The order of column data in the flat file must match the order of columns in the master XML file, because ssaservice uses the ordering information when it parses the flat file to get column values. For optimal Data Vault performance, the recommended size of a flat file is from 100MB to 5GB and the recommended number of rows is 1 million to 10 million.
You must create a signal file named
<BCP-FILE-NAME>.ok
to signal to the bulk file uploader that the flat file is ready to be loaded to Data Vault. When you are ready to run the bulk file uploader, save the
<BCP-FILE-NAME>.ok
file in the directory where the flat file is located. This directory is specified by the FILE_PATH value in the master XML file. The contents of the file itself are irrelevant and you can leave the file empty.

0 COMMENTS

We’d like to hear from you!