Professional Documents
Culture Documents
Agenda
Introductions Views vs. Derived Tables DTs as an efficient mechanism for dynamic grouping of data. Identify techniques and best practices for data and universe object security including implementing row level data restrictions. Implementing pass-through authentication for database object security. Dynamic aggregate table awareness for measure and dimension objects. Q&A
Introductions
Tom Wolniewicz, Senior BI / DW Solutions Architect, BroadstreetData Customer Ambassador: Anand Menon, Analytics CoE Development, Celestica
Usage:
SELECT * FROM VIEW_1
Hands-on Example
Universe Security
Access Restrictions in Universe Designer allow for restrictions to be put in place on an individual user or group basis. The following items can be managed:
Connection Controls (number of records) SQL generation (allow the use of sub queries, etc.) Objects (disable use of objects defined in the list) Rows (automatically append a WHERE clause to specific tables Table Mappings (automatically map to another table/view that has the same structure)
Universe Security
Sample access restriction shown below:
Universe Security
Pass-through authentication can also be used in one of two ways:
Enterprise AD/KERBEROS Delegation
Universe Security
Enterprise authentication to DB pass-through uses DB_USER and DB_PASS properties as defined in the CMC:
It will utilize DB named user accounts as defined in the database and is configured on an individual basis.
Universe Security
AD/KERBEROS authentication can also be passed through if using SSO using delegation. Presently this is only supported on the Microsoft Platform (Windows) with SQL Server database. Benefits include the ability to use AD groups to manage security within the database (access to tables/views/columns)
Universe Security
Pass-through configured in Designer Connection Parameters:
Aggregate Awareness
Business Objects Universe supports the notion of Aggregate Awareness which can dynamically select an aggregate table (summary) to improve query performance depending on the level of granularity of objects selected in the query.
Aggregate Awareness
We can use the Transaction Amount Measure and define it to be Aggregate Aware using the @ function.
Aggregate Awareness
Afterwards we need to define incompatibilities to trigger the detail level of aggregate awareness (otherwise only the summary is used)
Aggregate Awareness
Now when I generate a report using only the Transaction Amount I get the following SQL:
But when I add any other dimension the SQL automatically changes to use the detail table for the measure:
Reference Resources
Business Objects XI 3.1 Universe Designer http://help.sap.com/businessobject/product_guides/boexir31/en/xi3-1_designer_en.pdf
Q&A
Thank You!