Explain slowly changing dimensions Type 1, Type 2, and Type 3. Which statement accurately describes Type 2 behavior?

Get ready for the GMetrix Data Modeling Test. Enhance your skills with flashcards and multiple choice questions, complete with hints and explanations. Prepare effectively for success!

Multiple Choice

Explain slowly changing dimensions Type 1, Type 2, and Type 3. Which statement accurately describes Type 2 behavior?

Explanation:
Type 2 keeps full history by adding a new row when a dimensional attribute changes. Instead of replacing the old information, a new version of the dimension member is inserted with its own surrogate key and the updated values. The old row remains in the warehouse, marked as no longer current (often with a valid-to date or a current flag), so you can see what the dimension looked like at any point in time. For example, in a customer dimension, when a customer moves from one city to another, you create a new row for that same business key with the new address, and you mark the previous row as ended or not current. This way, queries can reconstruct the customer’s attributes as of a particular date and analyze changes over time. This is different from overwriting the old data (which is Type 1 and loses history) and from storing only a small amount of history in a single attribute (which resembles Type 3, where you keep limited past data in a separate field). It’s also not about deleting previous values, which would discard historical information. Type 2’s strength is preserving a complete history of changes for accurate temporal analysis.

Type 2 keeps full history by adding a new row when a dimensional attribute changes. Instead of replacing the old information, a new version of the dimension member is inserted with its own surrogate key and the updated values. The old row remains in the warehouse, marked as no longer current (often with a valid-to date or a current flag), so you can see what the dimension looked like at any point in time.

For example, in a customer dimension, when a customer moves from one city to another, you create a new row for that same business key with the new address, and you mark the previous row as ended or not current. This way, queries can reconstruct the customer’s attributes as of a particular date and analyze changes over time.

This is different from overwriting the old data (which is Type 1 and loses history) and from storing only a small amount of history in a single attribute (which resembles Type 3, where you keep limited past data in a separate field). It’s also not about deleting previous values, which would discard historical information. Type 2’s strength is preserving a complete history of changes for accurate temporal analysis.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy