OLAP Cube Reporting
To install the OptimiDoc data cube, perform the following steps:
1. Open the SQL Server Management Studio (SSMS) to connect to the database server on which the OptimiDoc database is located. All SQL scripts are stored to OptimiDoc\Support\OLAP. |
|
2. Open SQL001_CreateDBObjects.sql 2.1. On the first line, replace [OPTIMIDOC] with the name of your OptimiDoc database instance. 2.2. Execute the script. |
|
3.Open SQL002_GenerateDates.sql 3.1. On the first line, replace [OPTIMIDOC] with the name of your database instance 3.2. If necessary, change the values in the @DateFrom and @DateTo variables to the desired period. Note: Data outside this range will not be loaded into the data cube. 3.3. Execute script. |
|
4.Open and execute SQL003_CreateJob.sql |
|
5.Open SSAS001_CreateOLAP.xmla, connect to Analytics Server and execute the script. |
|
6.Open SSAS002_ConfigureDataSource.xmla and perform the following steps: 6.1. On line <ConnectionString> replace localhost with the name of the server 6.2. On line <ConnectionString> replace OPTIMIDOC with the name of your OptimiDoc database. 6.3. Execute script. |
|
7.Open and execute SSAS003_ProcessOLAP.xmla. |
|
Common problems
The following is a list of common problems when installing or working with the OLAP cube:
- Script SSAS003_ProcessOLAP.xmla ends with an error message saying it cannot connect to the database
- The user under which the Analysis Services service is running (SSAS service log on account) is used to load data into the cube. It is necessary to add access rights for this user to read data from the OptimiDoc database (the db_datareader role is sufficient)
- The cube doesn’t display current data
- The reason might be that the SQL job that keeps the data up-to-date is not running.
- It is also possible that there is no entry for the current day in the table containing dates. You can fix this by generating the SQL002_GenerateDates.sql again and entering the current date. This problem typically occurs on January 1st.





