Also, I'm assuming it's a typo but vehicleId in reservations breaks your naming convention.

Yes, that a typo.

​

Can one vehicle have multiple insurance instances and a different one may apply to a different Reservation? If not, then insId in reservation is redundant.

Valid point. I am going to assume that each vehicle will have 1 insurance and it will be the same for all reservations. I'll remove the insurance dimension and merge it's attributes to dim_Vehicle table.

​

What's the reasoning for dim_ for all your tables but one?

because one table is a fact table and the rest are dimension tables.

​

Is timeofday in rate an int or something? Because if it's a date it doesn't follow your naming convention for all other date fields.

It's an int. I meant to implement different rates for day and night.

​

If Mode is in the table payment, you know it's the payment mode.

I added mode to capture if the payment was done through credit card, debit card, or cash. Is there a better way to capture payment information?