is multiple db users a good idea

Anon

Hello all, I have just converted a ASP web ap (using oracle backend) to having one db user per real user on the application. Previous it had only one user, and all application users connected to the db as that user.

Are there any real advantages to either approach? I think it was a make work project and there was no real rational from my boss.... is this a good way to go?

all input greatly appreciated!

greg252

Automatically, I thought of one minus- the user database just becomes bloated.
BUT, tracking user activites is now very easy, isn't it?

Anon

Hi,

How many users are we talking about here? Are you just referring to the “username” and “password” you use to connect to the actual database or are you referring to something that connects after this point? If you are talking about usernames and passwords that connect to the actual database than I think this is a good idea.

The reason’s for this are simple.. Security and manageability, if you need to limit access to something in the database then you have the option. Down the road you will not have to re-tool the application.

But how many users are we talking about here?

Thanks
- Justin

Anon

you wrote:
//Are you just referring to the “username” and “password” you use to connect to the actual database

yes, exactly.... and it will include hundreds of users.

is this common in alot of applications to use multiple db users?