Writes the data values of a database to a text file.
EXPORT exportName amount formatOption
exportName |
Specifies the name, including the path, of the file for the exported data. If no path is specified, the file is created in the ARBORPATH\app directory. |
||||||
amount | Specifies the number representing the data to export.
|
||||||
formatOption | Specifies the format of the data.
|
The EXPORT command copies data in text format as an alternative to database archiving wherein you copy the files in binary format. Text format is more flexible because it is more easily ported to other databases and users can easily read it. The EXPORT command exports only the data, rather than the entire database. Because only data is exported, it is more complex to restore the database from an export file than from a true database archive. You must reload and recalculate the data if you use an export file to restore a database.
Some file management systems do not support text files larger than 2 GB.
If the exported data exceeds 2 GB, Analytic Services creates multiple
export files, as needed. An underscore and number is appended to the file names
of the additional files, starting with _1. For example, if exportName
is outfile.txt
and three files are created, the resulting file
names are outfile.txt, outfile_1.txt,
and outfile_2.txt
.
The export process does not begin until all users are logged out of the database. After the export process begins, the database is in read-only mode. Users can read the data but they cannot change it. After the export process is finished, Analytic Services returns the database to read-write mode and users can make changes to the data.
To create an export file called E060693
that contains only level zero data in columnar format:
EXPORT "E060693" 2 1;
If the exported data in this example exceeds 4 GB, three files are created:
E060693, E060693_1
, and E060693_2
.
©2004 Hyperion Solutions Corporation. All Rights Reserved. http://www.hyperion.com |