Data Model Properties

You can access the Data Model Properties page when you click Properties in the components pane of the data model editor.

Enter the following properties for the data model:

Property	Description
Description	Enter a description for the data model. The catalog displays the descriptions of data models. This description is translatable.
Default Data Source	Select the data source from the list. Data models can include multiple datasets from one or more data sources. The default data source you select here is presented as the default for each new SQL dataset you define. Select Refresh Data Source List to see any new data sources added since your session was initiated.
Oracle DB Default Package	Enter a default PL/SQL package for data models that include event triggers or a PL/SQL group filter. The package must exist on the default data source. If you define a query against an Oracle Database, then you can include before or after data triggers (event triggers) in your data model. Event triggers make use of PL/SQL packages to execute RDBMS level functions.
Query Timeout	Enter a time limit in seconds within which the database must execute SQL statements. This property applies to SQL query-based data models for scheduled reports. If the SQL query is still processing when the timeout value is met, the error Failed to retrieve data xml. is returned. Enter a value in seconds. If you don't enter a value for this data model, the server property value is used.
Enable SQL Pruning	Select this property to enhance processing time and reduces memory usage. This property applies to Oracle Database queries only that use standard SQL. If your query returns many columns but only a subset are used by your report template, SQL pruning returns only those columns required by the template. Note that Enable SQL Pruning is also a server-level property. Therefore, by default the data model-level property is set to Instance Level to inherit the server or instance level setting. To turn SQL pruning on or off for this particular data model, select On or Off from the list. SQL pruning is not applicable for PDF, Excel, and E-text template types.
Skip Unused Dataset Query	Select this property to omit the execution of any unused datasets in the layout, so you can reduce processing time and memory usage. By default, all datasets in a data model are executed whether a dataset is required for the output. When a data model contains multiple datasets for different layouts, each layout might not require all the datasets defined in the data model. You must set the Enable SQL Pruning property to On to use the Skip Unused Dataset Query property.
Enable SQL Session Trace	Select this property to enable SQL session trace. For each SQL statement, the trace contains: Parse, execute, and fetch counts CPU time and elapsed time Physical reads and logical reads Number of rows processed Library cache failures User name for which each parse occurred Each commit and rollback This property applies to Oracle Database queries that use standard SQL. Administrators and BI Authors can enable diagnostics before running the report, and then download the diagnostic logs.
SQL Trace Name	Enter a name for the SQL trace.
Enable XML Pruning	Select On to prune XML datasets larger than 2GB. If you enable XML data pruning, Publisher removes the unnecessary data elements and builds the XML structure using only the data fields that are mapped to the layout fields. Data pruning improves performance, especially for extremely large data extractions. Report consumers can configure XML data pruning when scheduling a job. XML data pruning isn't supported for XPT template (Publisher Layout).
Backup Data Source	Select the Enable Backup Connection property to use the backup data source. To use the backup data source only when the primary is down, select Switch to Backup Data Source when Primary Data Source is unavailable. Note that when the primary data source is down, the data engine must wait for a response before switching to the backup. To always use the backup data source when executing this data model, select Use Backup Data Source Only. Using the backup database may enhance performance. You must enable a backup for the data source.
Enable CSV Output	Select this property to generate report output only in a CSV file.
Optimize Query Execution	Select this property to allow the data processor to optimize the execution of SQL queries of parent and child datasets. Select this property only when the data model includes a parent-child hierarchy structure in a SQL dataset. Don't select this option for non-structured and non-SQL datasets.
Multithread Query Execution	Select this property to create multiple database connections to query the child datasets in parallel. If you select this property, the number of database connections per data model increases. This property is enabled only when: Optimize Query Execution is set to true. Data model has more than one dataset. Data model has parallel child dataset queries linked to the parent dataset. Data model uses the default data source. This property cannot be used when: Data model uses event triggers. Data model has a dataset query linearly linked to the parent dataset. Data model uses multiple data sources.

XML Output Options

These options define the characteristics of the XML data structure. Any changes to these options can impact layouts that are built on the data model.

• Include Parameter Tags — If you define parameters for your data model, select this option to include the parameter values in the XML output file. See Add Parameters and Lists of Values for adding parameters to your data model. Enable this option when you want to use the parameter value in the report.

• Include Empty Tags for Null Elements — Select this option to include elements with null values in your output XML data. When you include a null element, then a requested element that contains no data in your data source is included in your XML output as an empty XML tag as follows: <ELEMENT_ID\>. For example, if the element MANAGER_ID contained no data and you chose to include null elements, it would appear in your data as follows: <MANAGER_ID />. If you do not select this option, no entry is displayed for MANAGER_ID.

• Include Open & Close Tags — Select this option to include the open and close tags in your output XML data.

• Include Group List Tag — (This property is for 10g backward compatibility and Oracle Report migration.) Select this option to include the rowset tags in your output XML data. If you include the group list tags, then the group list displays as another hierarchy within your data.

• Exclude Tags for LOB Columns — Select this property to exclude the XML element tags for LOB columns. The data model must contain a single dataset of SQL query type and a single Character Large Object data element containing data extracted from an XML file. You can't use global level, summary, or aggregate functions, elements based on expressions, or group filters.
• Exclude Line Feed And Carriage Return for LOB — Select this option to exclude carriage returns and line feeds in the data.

• XML Tag Display — Select the display format to generate the XML data tags - uppercase, lowercase, or to preserve the definition you supplied in the data structure.

XML Data Chunking

XML data chunking supports distributed processing.

XML data chunking is suitable for large and long-running reports. If the administrator selects the Enable Data Chunking runtime property at the instance level, you can enable XML data chunking for individual data models, reports, and scheduled jobs.

In a data model, if you click Chunking, select Enable Chunking, and then specify an attribute in the Split By field, the data model pre-processor uses the split key to split large amounts of XML data into several chunks of data of manageable size.

Before you enable XML data chunking, understand its limitations and recommended usage.

XML data chunking:

• Is best suited for listing reports using a table and with no cross-references.
• Supports sorting, grouping, aggregation, and cross-referencing operations only within the individual chunked output. The merged output doesn't support these data operations.
• Adds page numbers to the PDF pages of the merged output. In the report template, remove the page numbering element to avoid duplicate or overlapping page numbers in the PDF output.
• Supports running totals, and other functions only within the individual chunked output, and each is reset with each chunked output.
• Supports only RTF, XPT, and eText, and XSL templates.
• Supports only PDF, XLSX, and Text output formats.
• Doesn't support multiple output formats. If you select XML chunking for a scheduled job, multiple outputs aren't allowed.
• Isn't supported for online reports.

Add Attachments to the Data Model

The Attachment region of the page displays data files that you've uploaded or attached to the data model.

Attach Sample Data

After you build your data model, you must attach a small, but representative set of sample data generated from your data model. The sample data is used by Publisher's layout editing tools. Using a small sample file helps improve performance during the layout design phase.

The data model editor provides an option to generate and attach the sample data. See Test Data Models and Generate Sample Data.

The administrator can set a limit to the size of the sample data file.

Attach Schema

The data model editor enables you to attach sample schema to the data model definition.

Publisher doesn't use the schema file. However, you can attach the schema for developer reference. The data model editor doesn't support schema generation.

Data Files

If you upload a local Microsoft Excel, CSV, or XML file as a data source for this report, the file displays here.

Use the refresh button to refresh this file from the local source. For information on uploading files to use as data sources, see Create Datasets.

The figure below shows the Attachments region with sample data and data files attached:

Description of the illustration xdo11g_dm_att.gif