Single wide table and dimensional schema

Hi SamyAbdul​,

I agree with Murtaza_Ghafoor​ on keeping the four Silver tables. The reason that matters most for your question is grain: datasets with different granularity and independent releases only combine cleanly in a wide table if you throw away information (or invent rows), whereas separate facts keep each grain honest.

A shape that usually supports both the differing observation periods and a single-row report view:

Silver : 4 cleaned tables, each at its own grain, with source_release and observation_period columns
Gold   : dim_hotel (shared), dim_date / dim_period, one fact table per dataset at its own grain
         each fact keeps hotel_key + period_key + source_release
Serving: a view (or semantic model measures) that joins the facts to dim_hotel for a chosen
         snapshot, pivoting admissions measures only at query time

That way the shared Hotel dimension supports cross-dataset reporting without an extra bridge, the release and period columns answer which data was used, and the wide row-per-hotel snapshot becomes a presentation choice that can change without reloading Silver.