• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
  • Mikalai Zaikin

database design problem for asp model

Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have been facing this problem from several projects. We often need to design databases for ASP model with lots of users from multiple organizations. There are three obvious choices available to me.
1. create org key in all the tables to differentiate data from each org
2. create a set of tables for each org, then use a association org table to switch
3. create one database for each org, use a controller database to switch
Each of these three has some pros and cons. The first one is easier to maintain and implement. The last one will at least piss off DBAs.
I personally will choose either the first or the last. The main thing in the first choice that worries me is database table locking time.
I am sure many other people will face the same problem, what's your take on that?
I didn't do it. You can't prove it. Nobody saw me. The sheep are lying! This tiny ad is my witness!
a bit of art, as a gift, that will fit in a stocking
    Bookmark Topic Watch Topic
  • New Topic