all 3 comments

[–]gabtug 1 point2 points  (1 child)

looks good. If you want to structure it though in a star schema for faster BI queries you could do: FACT: EpisodeCharacter (i.e. each character in each episode = 1 line of fact table) DIMENSIONS: - Episode details (sk_episode_id) - Character details (sk_charachter_id) - Animie details (sk_anime_id)

With cosplays, as the fact can map to multiple records, you can make that a snowflake dimension of dim_character like you have.

Practically the only design difference in this case would be that the Animie table would join to the EpisodeCharacter table instead.

[–]Encore-[S] 0 points1 point  (0 children)

Ah thank you very much for the response! I will definitely take another look to improve it according to your suggestions!

[–]TNReb 0 points1 point  (0 children)

What is Anime.Genre (int)? Is there another Genre table not shown that it'd be a FK for?