SQL Database architecture with multiple end Users

Question

I am making a web application where users get and manage data from multiple tables as well as create other users to access said data. currently I have it set up for one group of users.

My question is would it be better to have multiple databases in which each database has its own user which is stored in a master table("I don't like the sound of this one") or have a column in each table defining the user group that has access to it? Are either of these a good idea or is something else more appropriate?

Andrés Murman · Accepted Answer · 2016-08-23 03:47:13Z

1

You should have a column in each table. In my opinion, its the correct thing to do, and also you have only one database to do mantainance. Just imagine the time it would take to add a column to a table in the future, and you should do it in multiple databases.

answered Aug 23, 2016 at 3:47

Andrés Murman

1063 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

SQL Database architecture with multiple end Users

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related