Performance Considerations for OBIEE / Siebel Analytics:
1: Good Data Model Design on Star schema
2: NO Global Consistency Errors and Warnings
3: Metadata Repository size to be Reduced to the possible Extent b y removing the unused Objects
( tables, views, Aliases, synonyms, system Tables, Keys, Fk Keys) Init blocks and Variables
4: Best Practise and correct settings for the parameters in each section of the NQSConfig.ini
5: Applying Database hints ( use_nl, Oracle hints) for a table in the Physical layer of the Repository.
6: Reduce the SELECT statements executes by the OBIEE Server, and it chooses the correct MES.
7: Limit the generation of lengthy physical SQL queries by Modeling dimension hierarchies (Hierarchy ( Drill Key and Level Key))
8: The number of rows or record set returned from the Database can be restricted by putting the WHERE clause in the sources of the table.
9: Using Aggregate Navigation functionality of OBIEE and also design a good aggregation strategy for the Project.
10: Disable or remove the unused initialization blocks and also reduce the number of init blocks in the Repository
11: set the correct and recommended log level in the Production, setting the Query Limits and turn off logging
12: connection Pools, shared logon and number of connection pools Maximum connections and FIFO.
13: explore the features in the database properties of the repository, and push the complex functions to be performed at the database side.
14: Modeling ur Meta data using the materialized views in Physical layer
15: Good Caching and Purging strategy, Web server cache and Siebel Analytic Server Cache) and use of the Event Polling tables for the Project.
16: SQL Performance tuning for the Physical SQL generated by the Siebel analytics Server
