Results 1 to 8 of 8
  1. #1
    Join Date
    Oct 2004
    Posts
    91

    Unanswered: Pro / Con of different databases per customer

    Hello everyone -

    Is there a pro / con reason why a corporation would create a new database for each customer??

    I can understand the obvious reason - to keep the companies apart,
    but other than that single reason are there any other ones?

    thanks
    tony

  2. #2
    Join Date
    Feb 2004
    Location
    One Flump in One Place
    Posts
    14,912
    Maintenance nightmare.
    Testimonial:
    pootle flump
    ur codings are working excelent.

  3. #3
    Join Date
    Mar 2003
    Location
    The Bottom of The Barrel
    Posts
    6,102
    Provided Answers: 1
    Security, maintenance, backups, portability and performance monitoring immediately come to mind.
    oh yeah... documentation... I have heard of that.

    *** What Do You Want In The MS Access Forum? ***

  4. #4
    Join Date
    Feb 2004
    Location
    One Flump in One Place
    Posts
    14,912
    Them too
    Testimonial:
    pootle flump
    ur codings are working excelent.

  5. #5
    Join Date
    Nov 2004
    Location
    on the wrong server
    Posts
    8,835
    Provided Answers: 6
    there are other ways of keeping different customers from see eachothers data. One database is usually the best approach because of maintenence and keeping schemas and configuations synchronized. However I could imagine scenarios where you would not want customers who only have a couple of gigs of data to have their performance impacted by customers who have dozens of gigs of data. If you have something silly like your customers have direct access to the SQL Server, I could imagine there would be security benefits from having seperate databases as well. I guess like many things, it depends...
    “If one brings so much courage to this world the world has to kill them or break them, so of course it kills them. The world breaks every one and afterward many are strong at the broken places. But those that will not break it kills. It kills the very good and the very gentle and the very brave impartially. If you are none of these you can be sure it will kill you too but there will be no special hurry.” Earnest Hemingway, A Farewell To Arms.

  6. #6
    Join Date
    May 2004
    Location
    Seattle
    Posts
    1,313
    multiple databases work great for this...

    ...until you have more than one customer.

  7. #7
    Join Date
    Oct 2004
    Posts
    91

    ah hah

    Quote Originally Posted by Teddy
    Security, maintenance, backups, portability and performance monitoring immediately come to mind.

    Thanks for the other angles!

    take care
    tony

  8. #8
    Join Date
    Feb 2004
    Location
    One Flump in One Place
    Posts
    14,912
    Just to be totally explicit, anything client related would typically have a natural key of whatever you are currently using (based on your other thread you have one db per client) PLUS a client id\ code. Thus your tables (apart from generic lookups) would effectively be partitioned logically (if not physically) by client.
    Testimonial:
    pootle flump
    ur codings are working excelent.

Posting Permissions

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