Hotel Booking Snowflake Schema

Hotel booking snowflake schema

This hotel booking snowflake schema records each stay in FactStay with its nights and room revenue. The fact links to check-in date, guest and room. Guest details connect to country, while room details connect through room type to property. These separate levels make it possible to report revenue by property, room type, guest country or arrival period without repeating descriptive values throughout the fact table. The model is useful for hospitality groups that maintain shared property and room-type hierarchies across locations. It also keeps local room details separate from the cross-property categories used for management reporting. This improves consistency when properties share a central reporting model across a portfolio.

Tipo ERDNorma Chen 1976 / Everest 1976 (crow's foot)Motor schematex-erdActualizado 24/9/2026

La solicitud

“A hotel booking snowflake schema: FactStay linked to Date, Guest, and Room; normalize Guest through Country and Room through Room Type to Property.”

Entonces pruebaAdd a booking channel dimensionAdd a rate plan below Room Type

Qué hay en este dibujo

Lee las decisiones que hay detrás.

01Stay grain

Store one row per guest stay.

02Guest geography

Keep country outside the guest row.

03Room hierarchy

Separate room, type and property.

Use this for occupancy and revenue reporting across multiple properties.

Explorar todas las plantillas de ERD →

Preguntas frecuentes

Preguntas habituales

What is the fact table grain?

Each FactStay row represents one guest stay.

Why separate room type from room?

Many rooms can share a type, such as deluxe king.

Can this support property reporting?

Yes. Room Type links to Property for property-level rollups.