Users in database server or database tables

Posted by Batcat on Stack Overflow See other posts from Stack Overflow or by Batcat
Published on 2010-06-08T10:24:03Z Indexed on 2010/06/08 13:22 UTC
Read the original article Hit count: 392

Filed under:
|
|

Hi all,

I came across an interesting issue about client server application design.

We have this browser based management application where it has many users using the system. So obvisously within that application we have an user management module within it.

I have always thought having an user table in the database to keep all the login details was good enough.

However, a senior developer said user management should be done in the database server layer if not then is poorly designed. What he meant was, if a user wants to use the application then a user should be created in the user table AND in the database server as a user account as well.

So if I have 50 users using my applications, then I should have 50 database server user logins.

I personally think having just one user account in the database server for this database was enough. Just grant this user with the allowed privileges to operate all the necessary operation need by the application. The users that are interacting with the application should have their user accounts created and managed within the database table as they are more related to the application layer. I don't see and agree there is need to create a database server user account for every user created for the application in the user table.

A single database server user should be enough to handle all the query sent by the application.

Really hope to hear some suggestions / opinions and whether I'm missing something? performance or security issues?

Thank you very much.

© Stack Overflow or respective owner

Related posts about database-design

Related posts about management