Type 2 Change Handling

Hello, I have a design question for how to handle a type 2 change in the following situation:

I have a small dimension called ApplicationStatus with about 50 records. My fact Application table will have about a million records per year and it contains a FK to ApplicationStatus. The business wants to track the history when the status changes. The status will change on every fact record and it can change multiple times. I am hoping to avoid showing this tpye 2 change in the ApplicationStatus dimension, or it will get VERY large. Can anyone offer any design guidelines in this situation?

Thank,
Jason

Yes, you can track status changes in a fact table.

BoxesAndLines, I was not aware of that, thank you. Do you know of any Kimball articles or other good references on how to implement that?

I should point out, in case it matters, that the ApplicationStatus dimension has other attributes (about 10) besides just the status. Can I still efficiently track status changes in the fact table?

It would be a simple transaction fact. For each status change, insert a new row. The thing that is changing usually is represented as a degenerate dimension on the fact table (e.g. application number). If the status' are fixed in number and relatively small in cardinality (<10 or so) you can also look at an accumulating snapshot.