DB design - create new tables or not?
Creating a new DB. I have a tour company that has a lot of names and a few dozen hotels. My first thought was just to use the Names table for my hotels, using a Company field rather than first/last name fields. I'm starting to think I should just create a Hotels Table, rather than use the Names table as a generic placeholder for all types of names. If creating Hotels table makes sense, since Names (of people) and Hotels both have addresses, would you suggest then to have an Address table that relates to both Names and Hotels, or is that just over engineering and unnecessary - just have Names with address fields, and Hotels with address fields?
Is there a "generally preferred" way of doing this?