sql - Database design ideas for "master and slave" nodes -
we in design phase of product. idea have master (calling it) contains user information including user/registration/role/licence etc. , have slave database (calling it) contains main application related data.
some columns master database used in slave database. e.g. userid used everywhere in slave database. there multiple versions of salve in different tiers (depending on customers subscription). e.g. customer have dedicated slave databases application.
also data/tables/columns slave used in master.
how manage scenario can have maximum referential integrity (i know not possible time) without using linked servers. (we dont want use linked servers because improper design can abused , can effect performance result).
or bad idea. have single database design (no master/slave) different nodes. , customer's data in different nodes depending on subscription? problem see registration/user tables fragmented in different database nodes. e.g. usera in database01 , on.
any idea?
Comments
Post a Comment