Star Transformation in Siebel Analytics (OBIEE)
Star Transformation is a join method mostly used in Data Warehousing Environments to fine tune typical query performance. It is of utmost importance in DB environments where reporting tools like Siebel Analytics (OBIEE) is in use. It can also be used for other tools such as Business Objects. The conventional join mechanisms that the star transformation seeks to supersede are Hash join, nested-loops and sort merge join.
This paper shows how to take full advantage of this RDBMS feature.
If you moved to BI Publisher 11g or OBIEE 11g from BI Publisher 10g, you would have realized that debug option is no longer part of BI Publisher Administration UI. In 10g we can set the debug log level from Administration UI under Server configuration section but in 11g no more.In OBIEE 11g, it is central logging process which is part of Fusion Middleware.
-> Datawarehousing projects are categorized into 4 types.
1) Development Projects.
2) Enhancement Projects
3) Migration Projects
4) Production support Projects.
-> The following are the different phases involved in a ETL project development life cycle.
1) Business Requirement Collection ( BRD )
2) System Requirement Collection ( SRD )
3) Design Phase
a) High Level Design Document ( HRD )
b) Low level Design Document ( LLD )
c) Mapping Design
4) Code Review
5) Peer Review
a) Unit Testing
Star Schemas are proliferating with warehouses these days. Many practitioners I have met in this space are a bit new to the concept of star schemas and as such keep falling back to old habits. But this is only hurting them. So I'll try to give my simplistic view of how it works in the hopes of granting some clarity on the practice of Star Modeling and overcoming our previous training to resist its concepts.
There are various Oracle Warehouse Builder related routine tasks which I came across in my projects. So I feel that a write up on this will help Warehouse Builder Developer and Administrator across the word. Let handle OWB related task or questions one by one.
Automatic Back Up of OWB Project or Module or Mapping
I often come across the question like how can I back my work (mappings or oracle module or a project as a whole) daily? And automate the same. Like daily around 6:00pm i.e.
Partitioning is one of the most sought after options for data warehousing. Almost all Oracle data warehouses use partitioning to improve the performance of queries and also to ease the day-to-day maintenance complexities. Starting with 11G, more partitioning options have been provided and these should reduce the burden of the DBA to a great extent.
Aside from a nine month excursion to Sybase IQ, I've spent my entire career working with Oracle, so I don't profess too much expertise - indeed any! - about other RDBMS technologies. So in a weak attempt at self-education, I recently accepted an invitation to listen to a Teradata presentation directed at application developers.
In this article Mark explais how one can drill from a "Discoverer for OLAP worksheet" to a "Discoverer Plus Relational worksheet" using Discoverer 10.1.2.
"I have a question about drilling from an OracleBI Discoverer for OLAP 10.1.2 worksheet to a Discoverer Plus Relational worksheet. When you pass values from an OLAP worksheet you pass either the dimension name or the dimension value to the associated parameter in the relational worksheet. Obviously, in OLAP this dimension is treated as an object, and we have no idea which level the user may have picked before he drills out. On the other hand, in the relational world, each level of the dimension would be split out as a separate parameter. Could you run through a simple example where you drill from an OLAP worksheet to a relational worksheet and show how this is done?"
In this article, Mark explains how the SQL MODEL clause can be used to generate rather complex financial statements.