---
title: "Slowly Changing Dimensions Specialists, Offshore to Hire"
description: "Slowly changing dimensions specialists choose between type 1 and type 2 for each table. Hire one for your warehouse team, managed from our Chiang Mai office."
url: "https://azendo.co/skills/slowly-changing-dimensions/"
---

1. [Home](https://azendo.co/)
2. [Skills](https://azendo.co/skills/)
3. Slowly changing dimensions

# Slowly changing dimensions specialists for your dedicated team.

Slowly changing dimensions are the patterns for handling attributes that change over time. Type 1 overwrites and keeps no history; type 2 adds a new row with validity dates and preserves it. The choice decides what historical reports can say.

## Where slowly changing dimensions fits in a long-term product team.

The distinction matters more than its dry name suggests. If a customer moves from the small-business segment to enterprise, type 1 makes every historical order appear as enterprise; type 2 keeps last year's orders attributed to small business. Both answer a legitimate question, and reporting built on the wrong one is wrong in a way that is very hard to notice.

Type 2 costs more than the pattern suggests. Dimension tables grow with every change, queries must join on the validity window as well as the key, and loading logic has to detect changes and close the previous row correctly. It is the right choice often, but not by default.

## What your dedicated team does with slowly changing dimensions.

This is a business decision that is routinely made by whoever implemented the table. The result is a warehouse where some dimensions keep history and some do not, with no stated reason, and reports that disagree depending on which they touched.

Making it an explicit, recorded decision per dimension is what prevents that, and it is the sort of standard the data engineers on your team hold, as described in how an assignment runs.

## Common slowly changing dimensions use cases.

* Historical reporting that stays true Type 2 where facts must reflect attributes as they were at the time.
* Current-state reporting kept simple Type 1 where only the present value matters, without paying for history.
* A consistent, recorded policy Each dimension's treatment decided and documented, so reports cannot disagree silently.

## Adding slowly changing dimensions skills to your team.

Dimension design sits with [a dedicated data engineering team](https://azendo.co/services/dedicated-data-engineering-team/), with history requirements set by the business.

Slowly changing dimensions specialists join your team remotely as dedicated, full-time team members, selected, employed and managed by us in Chiang Mai and Bangkok. Companies that [hire offshore developers](https://azendo.co/hire-a-dedicated-development-team-in-thailand/) through Azendo add the skill when the product calls for it.

## Roles that use slowly changing dimensions

* [ETL Developer Data engineering](https://azendo.co/services/dedicated-data-engineering-team/etl-developer/)

## Service areas that use slowly changing dimensions

* [Data engineering](https://azendo.co/services/dedicated-data-engineering-team/)

Capacity is agreed across your whole team, with one monthly fee, not per skill.

## Related in data pipelines

* [Spark, a skill in our teams](https://azendo.co/skills/spark/)
* [Flink, a skill in our teams](https://azendo.co/skills/flink/)
* [Dagster, a skill in our teams](https://azendo.co/skills/dagster/)
* [Prefect, a skill in our teams](https://azendo.co/skills/prefect/)
* [Airbyte, a skill in our teams](https://azendo.co/skills/airbyte/)
* [Informatica, a skill in our teams](https://azendo.co/skills/informatica/)
* [Talend, a skill in our teams](https://azendo.co/skills/talend/)
* [SSIS, a skill in our teams](https://azendo.co/skills/ssis/)

## Tell us what you need slowly changing dimensions for.

A service delivery manager will reply with the specialists we'd suggest, the monthly capacity and what the first month looks like.

[Browse all skills](https://azendo.co/skills/)