Use to incrementally build one or more dimensions from a data file, without restructuring the database. This command provides better performance than BUILDDIM whenever you need to do multiple dimension builds from multiple rules files and your database contains data.
INCBUILDDIM location rulobjName dataLoc sourceName fileType errorLog appendLog [verify]
location | Location of the rules file. Values: 1 - Local/client-based rules file 2 - Remote/server rules file 3 - File. Use option 3 if the file is not an Analytic Services object, or if you want to specify the full path name. Otherwise, Analytic Services looks in the < APPNAME >/<DBNAME > directory. |
rulobjName | Name of the rules file. |
dataLoc | Location of the data file. Values: 1 - Local/client data file 2 - Remote/server data file 3 - File. Use option 3 if the file is not an Analytic Services object, or if you want to specify the full path name. Otherwise, Analytic Services looks in the < APPNAME >/<DBNAME > directory.4 - SQL source |
sourceName | Source of the data file. Values:
|
fileType | Data file type. Values: 1 - Excel file 2 - Lotus .WK1 file. 3 - Lotus .WK3 file. 4 - Text file 5 - Lotus .WK4 file. This parameter is not required if you are using an SQL source. |
errorLog | Name of text file to receive error messages and rejected records. Each INCBUILDDIM command in a BEGININCBUILDDIM...ENDINCBUILDDIM block can specify a different error log. |
appendLog | Specifies whether to append to the error log
file or overwrite it. Values: 1 - Append 2 - Overwrite |
verify | Optional parameter that specifies whether or not to verify the outline resulting from the incremental dimension build. Values: Y - Yes, verify the outline. This is the default. N - No, do not verify the outline. |
This command changes dimensions in the .OTN
file according to the specified
rules and data files. See BEGININCBUILDDIM for
information on the .OTN
file.
Each rules file can build one or more dimensions. If a rules files builds multiple dimensions and an error occurs in a record for any given dimension, Analytic Services rejects the entire record. As a result, other dimensions represented in that record might not build correctly. In such a case, consider designing dimension builds with multiple rules files using INCBUILDDIM.
One common example of this problem relates to the Add as Child build method. Break the rules file into multiple rules files if both of the following circumstances apply:
For example, if you are adding Mbr1 and Mbr2 as children of Par1 and Par2:
Par1 Par2 Mbr1 Mbr2
And if Mbr1 already exists in the outline as the child of some other parent than Par1, you need to break the rules file into two separate builds. Otherwise, when Analytic Services sees that the member already exists in the outline, it rejects the entire record.
By default, each step of an incremental dimension build must produce a valid outline. You can use the verify N parameter to create an interim outline that is not valid and then update the outline in a subsequent incremental build that makes the outline valid. To verify the outline in subsequent incremental builds, remove the verify parameter or specify a Y. Make sure that the last incremental build verifies the outline.
The INCBUILDDIM command is identical to the BUILDDIM command, except for the following:
The following command builds the dimensions specified in GENREF.RUL
and LEVELMUL.RUL
,
discards all data, and saves the new outline after the dimension builds are
complete:
BEGININCBUILDDIM; INCBUILDDIM 2 "GENREF.RUL" 2 "GENREF.TXT" 4 "ERR.OUT" 1 N; INCBUILDDIM 2 "LEVELMUL.RUL" 2 "LEVELMUL.TXT" 4 "ERR.OUT" 1 Y; ENDINCBUILDDIM 4;
Note that you can use the same rules file with multiple data files, as long as the data files conform to the formatting and rules saved in the rules file. For example:
BEGININCBUILDDIM INCBUILDDIM 2 "GENREF.RUL" 2 "GENREF1.TXT" 4 "ERR.OUT" 2 N; INCBUILDDIM 2 "GENREF.RUL" 2 "GENREF2.TXT" 4 "ERR.OUT" 1 N; INCBUILDDIM 2 "GENREF.RUL" 2 "GENREF3.TXT" 4 "ERR.OUT" 1 Y; ENDINCBUILDDIM 4;
BUILDDIM
BEGININCBUILDDIM
ENDINCBUILDDIM
©2004 Hyperion Solutions Corporation. All Rights Reserved. http://www.hyperion.com |