Skip to main content
SCD Type 2 transformations in Nekt help you maintain a complete history of changes in your dimension data. Unlike Type 1 (which overwrites old data) or Type 3 (which stores limited history), our no-code implementation automatically creates new records for each change, making it perfect for tracking historical changes in customer information, product details, or employee records.

​
Creating SCD Type 2 Transformations

Nekt provides a streamlined, no-code process for creating SCD Type 2 transformations. This guided setup makes it easy to implement data versioning without writing any code, while still maintaining the flexibility to customize the transformation if needed.

​
Step 1: Select Input Table

Choose the source table containing the data you want to version:
  • Select the table that needs historical tracking
  • Ensure your source data has a reliable way to detect changes
  • Verify data quality and completeness

​
Step 2: Define Primary Keys

Identify the columns that uniquely identify each record:
  • Specify the business keys (e.g., customer_id, product_id)
  • The system will automatically create a surrogate key for versioning
  • Ensure keys are stable and reliable for change detection

​
Step 3: Configure Output Settings

Set up the transformation output:
  • Select the output layer for the transformed data
  • Provide a descriptive name for the new table
  • Add a description to document the transformation’s purpose
  • Configure when and how often the transformation should run
  • Choose from schedule-based, event-based, or manual triggers
For detailed trigger options and plan-specific limitations, see our Triggers documentation

​
Best Practices

  1. Data Quality:
    • Ensure source data has reliable change detection
    • Validate data completeness before processing
    • Monitor for data anomalies
  2. Performance:
    • Optimize change detection logic
    • Use appropriate indexing strategies
    • Monitor transformation execution times
  3. Maintenance:
    • Document business rules for change detection
    • Keep track of version history
    • Regularly validate historical data
  4. Monitoring:
    • Track number of changes per run
    • Monitor storage growth
    • Set up alerts for unusual patterns

​
Need Help?

If you encounter challenges during the transformation process, our team is ready to assist. You can:
  • Check our SCD Type 2 documentation for reference
  • Review our example implementations
  • Contact our support team for additional guidance
⌘I