I have designed a database for a bunch of different properties. Each property has Employees, Customers, and assets. The assets are items that can be assigned to customers for a period of time then returned.

My question is I am wondering if setting up one database in one location using the property code as part of the primary key is a good idea or should I somehow split the database up into tables by locations.

One database is preferable. Not all tables necessarily want property code in their primary keys: for example, the same Customer could perhaps get assets from more than one property?

That is true, but perdominatly customers will get assets from one property. Think of this as a bunch of aprtment complexes and the assets are furniture. To prevent furniture form being traded amongst apartments each piece is assinged a unique number and is assigned to an occupant or customer.

OK, fine. But still one database not many!

That is waht I thought thank you.