Hi, 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?