The preconfigured (out-of-the-box) DataSelf BI system has been designed to have a balance of flexibility and high performance. I mean, it's a platform that can address a wide range of BI needs with a decent level of run time performance. For certain instances, the server-side system must be fine-tuned (adjusted) to address needs not well covered by the out-of-the-box settings. This can be done by adding more data structures to the server and/or adjusting the data structures to run certain types of queries more quickly. Overall, most queries should run quickly (typically in seconds, or up to a minute) regardless of the size of the source databases. If this is not occurring, the server software and/or hardware may need adjustments.
There are 3 main tasks involved when opening ProClarity:
- Opening the application per se. You can check how long does it take by opening ProClarity via Windows Start > All Programs > ProClarity > ProClarity. By doing this, you’ll open it without a briefing book and without a connection to a cube.
- Loading the ProClarity briefing book. Your bbk file is about 25MB big. You can probably test the speed to transfer this file over a network by copying and pasting it from the server to the local workstation.
- Opening a cube. In the DataSelf BI preconfigured bbk file, the first query opened by ProClarity is the last server-side data refresh time. The cube that has this information is very small, thus this task should take little time.
Another relevant note: After a server-side data refresh, it may take some time for Analysis Services (AS) to load data to RAM. As a rule of thumb, after a data refresh, AS will load data to RAM as needed. This means that it may take a bit longer when someone runs a query against every cube for the first time of the data refresh. Next query run (by the same person or anyone else against the same cube) may run faster since the cube data has been loaded to RAM.
The same concepts about apply to reports built in any other tool such as Excel.