.net - saas app needs to be converted to multidatabase structure -

.net - saas app needs to be converted to multidatabase structure -

our company has shared db saas app multi-tenancy. info sensitive (medical) , clients refusing sign contract if don't have separate databases them.

to me poses maintenance nightmare. i'm sure if start going downwards path, there many clients want it, not mention used in marketing sales. functionality same clients. not anticipate construction of app changing drastically if clients wanted custom functionality them. think can handle through bi , eav construction etc - time tell. have 50 clients in future. every alter have coordinate 50 databases.

i know 1 of options saas model due nature of business. there other options qualify 'separation' of info such partitioning each client's info different physical drives or that. still doesn't solve problem because there possibility of info overlap partitions - may true separate dbs if there bugs in app.

has been forced multi db approach? hear them if still think right thought or not. may not have selection if business requirement improve know i'm signing for.

i depends on organization... if willing , able build awesome upgrade tools, fine. otherwise, fighting tooth , nail single db. create life much easier. also, consider using pre-allocated columns / wide tables on eav. time saver in opinion.

the eloquent implementation have seen 1 used salesforce.com. if google search "salesforce multitenancy" find white papers , webinars straight salesforce.com describing architecture. first result search came , might starting point.

https://developer.salesforce.com/page/multi_tenant_architecture

these guys have multiple "pods" (full stack of web/db/caching servers). each 1 has thousands of customers running on if. if absolutely cannot utilize shared db, @ to the lowest degree worth checking out they've done.

.net database sql-server-2008 c#-5.0 saas