Best Practices and Common Pitfalls

​

When to Edit your Model

• If the model is incomplete, such that core entities are missing - Adding
• If the fundamental base sql is not wide enough, and core properties from the underlying tables are missing, you can expand the scope of the entity - Add-Edit
• If the SQL are not accurate enough - and does not capture your internal business logic - Editing
• One can also sharpen the textual definitions when needed - Editing

​

Best Practices

• Keep base queries as simple as possible

• Any attribute mapped under the entity needs to be included in the entity’s textual context

• Define commonly used attributes
• Give clear, business-friendly descriptions
• Use consistent naming conventions

• Create dimensions that align with common analysis patterns
• Consider performance implications of different grouping levels
• Document any special handling requirements

• Define commonly used relations
• Make sure to perform the join operation between 2 base queries (of the source and the target entities of the relation)
• Document cardinality (one-to-one, one-to-many, etc.)
• Consider join performance
• Handle null values appropriately

• Test any SQL statement to ensure correct syntax and column or table names