Should I use separate address dimensions?

I have a Star Schema model with two Dimensions (User and Store) each of them have addresses, which I store.

Each User and Store can just have one Address. Is it recommended to split the Dimension into a Address Dimension (with a 1:1 relationship)? Are there any technical arguments to handle like this? Or is it a common way to keep the address in the user/store dimension?

You should add the address to the user/store dimension as the address is a property of the dimension member, not the fact record.

Adding the address to the dimension allows you to define attribute relationships between country -> city -> user which should improve performance when you create hierarchies using those attributes.

It will usually also allow for easier calculated measures.

As a last point, having the address as attributes on the dimension will allow for easier handling of slowly changing dimensions if a user/store moves to a new address.

StackExchange Database Administrators Q#199419, answer score: 3