Best practices

Follow our best practices when starting a new project

Modeling Approaches

• Model a Data Store Solution
• Model a Dimensional Solution
• Model a Data Vault Solution
• Model a Data Mart Solution
• Model a Stage Solution
• Model a Stage JDBC Solution
• Model a Stage File Solution
• Model a Stage OpenQuery Solution

Use Cases

• Use Linked Projects
• Configure an incremental load
• Configure a multi-version load
• Configure a delete detection behavior
• Test a Generator upgrade
• Update a Project when the source changed
• Do a delta deployment
• Do a partial deployment
• Deploy a Project in production
• Take care of entries from Cleansing Error tables
• Reduce the volume of the Cleansing Error tables
• Avoid to load all data in development

Business Rules

• Dataflows amount
• Dataflow Sets amount
• Dataflow Sets Aggregation Amount
• Dataflow Set Model Objects amount
• Relationships amount
• Terms amount
• Supported Term Mappings
• Supported Term Data Types
• Supported Historization Types
• Supported Missing BK Behavior
• Supported Aggregation Types
• Business Key Terms amount
• Business Key Terms not nullable
• Identity Terms amount
• Identity Terms not nullable
• Supported Implementation Types
• Implementation Type Dataflows amount
• Implementation Type Incremental Filter
• Supported Deduplication Methods
• Supported Load Cachings
• Relationships from Link
• Relationships from PIT
• Foreign Key Mapping
• Historized Source
• ValidFromSourceTerm exists
• ValidFromSourceTerm configured
• Fact Load Strategy selected
• One Fact Load Strategy selected
• Effective Timestamp mapped
• Supported Fact Load Strategies
• Fact Load Strategy Insert needs Incremental selected
• Dataflows amount with multi-version load
• Dataflow Sets amount with multi-version load
• Deduplication with multi-version load
• Aggregation with multi-version load
• Supported Implementation Types for stage-driven load plans
• No incremental load with a Deduplication
• Not Cyclic Dataflow
• Not Cyclic Relation
• No delete detection with multi-version load
• No delete detection source with a deleted set
• Delete detection source exists
• Delete detection source name is unique
• Delete detection source Business Key exists
• No delete detection with an incremental load in the source
• Delete detection without historization set in the terms