## 10.6.2 Exporting analyzed documents to a relational database 

Before you begin exporting data to a relational database, you can export a small subset of data as XML to a file system for the following reasons: 

GLYPH<SM590000> To see the type of data that is being exported as fields, facets, and metadata. For any native fields that you map to the search fields, the names of the search fields are displayed in the exported data. 

GLYPH<SM590000> To determine the data that needs to be inserted into the database. For example, when you export analyzed documents, no binary data is exported. In this case, you must modify the default configuration. Similarly, you can modify the configuration to remove any fields or facets that you do not want to needlessly insert into the database. 

Content Analytics uses the field configuration that you set for the export to automatically insert exported data into a relational database. Content Analytics inserts the data into star-schema tables. 

Exporting analyzed documents to a relational database requires the following tasks, which are explained in the following sections: 

1. Configuring the database export information 

2. Running the export 

3. Validating the results of the analyzed documents export 

## Configuring the database export information 

The first step in exporting data to a relational database is to configure the database export information. You must define how the metadata of a document is mapped to the columns of tables in the database. The database information includes connection and configuration information about the database. 

To set up the database export configuration information for exporting analyzed documents, follow these steps: 

1. From the administration console, click Collections  in the toolbar. 

2. In the Collections view, locate the collection that you want to edit and click Edit . 

3. Select the Export  Arrow (Figure 10-17 on page 372), and go to Configure options to export crawled or analyzed documents . 

