About the reporting deployment options
When you run the Report SQL Generator tool, you specify whether you want the script to create views, materialized views, or tables. Which deployment option you use depends on the amount of data contained in your system.
For smaller implementations, reporting views that directly query the production data might perform sufficiently for your needs. If they do not, try materialized views.
For medium sized implementations, use either materialized views on the production system database or set up reporting tables in a separate database.
For large implementations, configure a separate reporting database.
For all implementations, you can use Cognos Connection Administration to schedule reports that retrieve large amounts of data to run during off hours.
Materialized views and MS SQL Server
The reporting feature does not support materialized views for MS SQL Server.
In SQL Server, materialized views are called "indexed views." However, the definition that creates an index in a view on SQL Server cannot use certain aggregations, functions, and options that the reporting views include. Therefore, if you are using a SQL server database, use views or reporting tables.
eMessage
and Oracle
If your installation includes
eMessage
and your database is Oracle, you must use materialized views or reporting tables.
Data synchronization
When you deploy with materialized views or reporting tables, determine how frequently you want to synchronize the data with the production system data. Then, use your database administration tools to schedule data synchronization processes to refresh the reporting data regularly.
Copyright IBM Corporation 2012. All Rights Reserved.
