Difference between revisions of "Tutorial/Schema cheatsheet"

From TempusServa wiki
Jump to navigation Jump to search
old>Admin
old>Admin
Line 23: Line 23:


== Defining dimensions for related data ==
== Defining dimensions for related data ==
=== Standard lookup value ===
==== Structure ====
{|
|Solution as displayed
|"Sample solution"
|-
|Solution system names
|sample
|-
|Database table names
|data_sample
|-
|}
* data_sample
** CATEGORY: Field containing the lookup value
==== Cube schema ====
    ...
    <Table name="data_sample"/>
    ...
    <Dimension name="Example" foreignKey="CATEGORY">
        <Hierarchy hasAll="true" primaryKey="LookupID">
            <Table name="formfieldlookup"/>
            <Level name="Category" column="Value" uniqueMembers="true"/>
        </Hierarchy>
    </Dimension>
    ...


=== Related solution ONE step away ===
=== Related solution ONE step away ===

Revision as of 02:00, 28 February 2014

Schema structure overview

  • Table (one):
    • Structure: The centre table
  • Dimensions (many)
    • Structure: Related tables or groupable values
    • OLAP: Columns/row "headers" in the cube
  • Measures (many)
    • Structure: Values in the centre table
    • OLAP: Numbers to display in cell cubes

Defining dimensions for related data

Simple text/number values

Date/period values

Enumeration values

Defining dimensions for related data

Standard lookup value

Structure

Solution as displayed "Sample solution"
Solution system names sample
Database table names data_sample
  • data_sample
    • CATEGORY: Field containing the lookup value


Cube schema

   ...
... <Dimension name="Example" foreignKey="CATEGORY"> <Hierarchy hasAll="true" primaryKey="LookupID">
<Level name="Category" column="Value" uniqueMembers="true"/> </Hierarchy> </Dimension> ...

Related solution ONE step away

Structure

Solutions as displayed "Some child" -> "Father or mother"
Solution system names child -> parent
Database table names data_child -> data_parent


  • data_child
    • PARENT: Key to the "parent" solution
  • data_parent
    • GRANDPARENT: Key to the "grandparent" solution
    • PARENTNAME: Descriptive field

Cube schema

   ...
... <Dimension name="Example" foreignKey="PARENT"> <Hierarchy hasAll="true" primaryKey="DataID" primaryKeyTable="data_parent">
<Level name="Parent" column="PARENTNAME" uniqueMembers="true"/> </Hierarchy> </Dimension> ...

Related solution TWO steps away

Structure

Solutions as displayed "Some child" -> "Father or mother"
Solution system names child -> parent
Database table names data_child -> data_parent


  • data_child
    • PARENT: Key to the "parent" solution
  • data_parent
    • GRANDPARENT: Key to the "grandparent" solution
    • PARENTNAME: Descriptive field
  • data_grandparent
    • GRANDPARENTNAME: Descriptive field

Cube schema

   ...
... <Dimension name="Example" foreignKey="PARENT"> <Hierarchy hasAll="true" primaryKey="DataID" primaryKeyTable="data_parent"> <Join leftKey="GRANDPARENT" rightKey="DataID">
</Join> <Level name="Grandparent" table="data_grandparent" column="GRANDPARENTNAME" uniqueMembers="true"/> <Level name="Parent" table="data_parent" column="PARENTNAME" uniqueMembers="true"/> </Hierarchy> </Dimension> ...

Defining measures