March 23, 2009 at 2:47 am
I do have separate customers and that’s my prime reason for creating a database for each, to ensure they never see each other’s data. I realise that I can code to ensure the data is never shared, but mistakes can happen, and a separate database is a belts and braces solution to preventing this.
One question this does through up is how are Microsoft currently licensing SQL server, will extra databases be expensive to implement just in licensing, or is costing per instance / per processor?
March 25, 2009 at 4:35 am
Andy Bod (3/22/2009)
Can you advise how, if I go for the multiple database option I can best keep the structure and sp's in sync? Can this be automated?
My advice is don't. It would make no sense for your application because it would achieve nothing useful at all. As your question suggests it would carry a significant burden of needless administration and maintenance.
April 24, 2009 at 2:59 am
Placing separate entities into same table, even if they LOOK same, is a big mistake in my eyes, because it leads to huge mess in the future, as business requirements change (and they WILL change, if you plan to support multiple clients/customers). True, separating them means more work, but your solution will be "open", not rigidly tied to your current needs.
Viewing 3 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply