Pros/Cons Using multiple databases vs using single database

Question

I need to design a windows application which represents multiple \"customers\" in SQL Server. Each customer has the same data model, but it\'s independent.

what will

Answer 1

One day your developer will screw up something and one customer will access info of another customer. You will lose your customers as result. This alone should tell you that multiple customers can't be in one data base. no one will want to be your customer if they know this.

Do I have to really go over all issues that will eventually happen if this is the case? The answer is simple here - NO. You don't want to have information of multiple customers in the same database.

Only time that this happens is if you have multiplexer database to keep track of customer logons, sessions, etc. But data used and stored by customers should be in the dedicated database.