Click here for aggregate storage version
Export all data, level-0 data, or input-level data, which does not include calculated values. Export files are stored in the ARBORPATH/app directory on the server. To use Report Writer, export the data using a report file.
Minimum permission required: Read. This statement requires the database to be started.
export database sample.basic data to data_file 'D:\\fileout','D:\\fileout2','D:\\fileout3';
Exports data concurrently to a list of file names.
export database sample.basic input data
to data_file 'exp_input.exp';
export database sample.basic using report_file "'$ARBORPATH/App/Sample/Basic/asym.rep'" to data_file 'home/month2.rpt';
Note: In the path to the report file in the above UNIX example, double quotation marks are used to allow variable expansion in the single-token FILE-NAME, and single quotation marks are required because there are special characters in the file name.
export database sample.basic using report_file 'AnalyticServices\\App\\Sample\\Basic\\asym.rep' to data_file 'c:\\home\\month2.rpt';
Note: In the file paths in the above Windows example, single quotation marks are required because there are special characters in the file name. Two backslashes ( \\ ) are required by the MaxL Shell to indicate one backslash, because the backslash has a special meaning to the MaxL Shell.
You can export data from a database in the following ways using export data.
|export database <dbs-name> all data...||Export all data in the specified database to the $ARBORPATH/app directory on the server. Note: Exporting data does not clear the data from the database.|
|export database <dbs-name> level0 data...||Export level-0 data blocks only (blocks containing only level-0 sparse member combinations. Note that these blocks may contain data for upper level dense dimension members.) A level-0 block is created for sparse member combinations when all of the members of the sparse combination are at the bottom of dimension branches.
Note: Exporting data does not clear the data from the database.
|export database <dbs-name> input data...||Export only blocks of data where the block contains at least one data value that was loaded (imported), rather than created as the result of a calculation.|
|export database <dbs-name> ... data in columns||
Export data in columns, to facilitate loading the exported data into a relational database. In each row, the columnar format displays a member name from every dimension. Names can be repeated from row to row.
Columnar format provides a structure to the exported data, so that it can be used for further data processing by applications other than Analytic Services tools. In non-columnar format, sparse members identifying a data block are included only once for the block. Because the export file in non-columnar format is smaller than in columnar format, reloading a file in non-columnar format is faster.
|export database <dbs-name> ...using...report_file...||Run a stored report script, exporting a subset of the database.|