Verifying reports in Report Builder using status information from Lifecycle Query Engine

You can verify the completion of your report using the detailed status information of Lifecycle Query Engine conditions that are displayed in the Report Builder.

When completeness checking is not enabled for both configuration scoped and non configuration scoped reports for relational storeLifecycle Query Engine, the Report Builder gets information about Lifecycle Query Engine data providers status. Based on this information, the Report Builder warns the user if there are any Lifecycle Query Engine data providers that are being indexed, validated, or removed.

Checking of LQE data provider status applies only to SQL queries for reports on relational store, and not to metadata or other nonreport queries.

When completeness checking is enabled, the current Lifecycle Query Engine data providers status is always fetched from Lifecycle Query Engine to get the latest data and stored in the cache.
Note: You can enable the completeness checking only for configuration scoped reports.

When a report with an Lifecycle Query Engine data source is incomplete due to different Lifecycle Query Engine conditions, appropriate warning messages are displayed in the Report Builder. You can rerun the report, when the Lifecycle Query Engine processes displayed in the warning messages are completed. Absence of a warning message indicates that the report data is complete.

The Report Builder displays the warning messages for the following Lifecycle Query Engine conditions:
  • Data sources that are indexing
  • Data sources that are validation data
  • Data sources that are being removed
The report also displays an information icon along with hover text, if the following Lifecycle Query Engine conditions affected the execution time of a report:
Note: These Lifecycle Query Engine conditions are only applicable to SPARQL.
  • Running queries
  • Long-running queries
  • Rogue queries
  • Database backup in progress
  • Database compaction in progress
  • High Lifecycle Query Engine load

For more information, see Detailed Lifecycle Query Engine status information in Report Builder.