Databases Reference
In-Depth Information
•
What field types should we use?
And the recommendations for designing Data Objects are as follows:
•
In most cases, you should use internal Data Objects versus external Data
Objects. External Data Objects are not directly managed by Active Data
Cache, so the real-time data changes are not captured and pushed to the cli-
ent. Thus, in the case of a real-time dashboard, using external Data Objects
as the main data source is not appropriate.
•
When defining the data fields for a Data Object, you should consider adding
more fields that might be used in the current or future reports. If more data
fields are needed in the future, consider creating a new version of the Data
Object, instead of editing the original Data Object. Therefore, a new report
can be built using the new Data Object, without impacting your existing re-
ports.
•
It is a best practice to define the Data Object fields using the same type as in
the upstream application. For example, the order shipment date with the type
of
DateTime
in the order management system should have a correspond-
ing field in the BAM Data Object, that is, of the type
DateTime
. This can
prevent expensive data conversion operations when moving data to BAM
Active Data Cache.
•
Minimize the usage of the lookup fields and calculated fields, as it may in-
troduce performance overhead, given the complexity of the underlying SQL
queries.
•
Creating indexes for Data Objects may improve the performance of Data Ob-
jects queries and report rendering. For example, if you want to filter the Data
Objects query result in a report, then creating indexes on the filtering criteria
may improve the report rendering performance.
Understanding the mappings between Data
Objects and internal database tables
All internally managed Data Objects are persistent to database tables of a
Relational Database Management System (RDBMS)
. BAM 11g R1 certified
RDBMSs are Oracle Database, IBM DB2, or Microsoft SQL server. The Data
