asked
SQL Schemas
We have a customer that owns businesses in multiple markets across geographic regions. They want to run our POS system in a single database using schemas to split the data into virtual data sets, 1 for each market. So instead of having 50 databases with the market names (Market1DB, Market2DB) they want Schemas called Market1, etc. Users log in to those schemas and work without affecting Markets 2-50. Is this a good approach? Thoughts? Thanks!
17 People are following this question.
