Publishing options

During the publishing process, you specify how often the data in the report is updated. You can choose to force users to see specific instances based on a schedule that you determine (recurring), or you can choose to let users set the schedule themselves (on demand).

Specifying the data that users see (recurring)

This option is recommended for objects that are accessed by a large number of people and that do not require separate database logon credentials.

Benefits

• Users view the same instance of the report, reducing the number of times the database is hit and using system resources more effectively.
• The report instance is static (contains saved data) and is stored on the Cache Server, allowing multiple users to access the report at the same time.

Drawbacks

• The instance the users see is based on the selection criteria (parameters and record selection formulas) and schedule set by the administrator.

Allowing users to update the data in the report (on demand)

This option is recommended for smaller reports that use parameters and selection formulas, require separate database logon credentials, or have frequent data changes.

Benefits

• Users are able to determine the frequency in which the data in the report is updated.

Drawbacks

• Multiple users generating reports at the same time increases the load on the system and the number of times the database is hit.

  Each unique report page is cached separately. It's possible that the Cache Server can contain many copies of the cached report, each of them being generated by hitting the Page Server and database.