Results 1 to 5 of 5
  1. #1
    Join Date
    Feb 2002
    Posts
    43

    Complex design question

    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.

  2. #2
    Join Date
    Sep 2002
    Location
    UK
    Posts
    5,171

    Re: Complex design question

    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?

  3. #3
    Join Date
    Feb 2002
    Posts
    43
    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.

  4. #4
    Join Date
    Sep 2002
    Location
    UK
    Posts
    5,171
    OK, fine. But still one database not many!

  5. #5
    Join Date
    Feb 2002
    Posts
    43
    Originally posted by andrewst
    OK, fine. But still one database not many!
    That is waht I thought thank you.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •