one oracle database user or multiple users used in asp.net -

one oracle database user or multiple users used in asp.net -

i have question performance each of 2 scenarios on oracle database :-

background : develop asp.net business application enterprise utilize oracle database

one:

i create 1 database user , utilize user in connection string of asp.net application connect db when doing business logic, if 20 end-users utilize asp.net application simultaneously, of them connect db 1 user

two:

i create multiple database users ( 2 - 5 users), , utilize them in pool of connection strings if 20 end-users utilize asp.net application simultaneously, not connect db 1 user

what better

i'm not sure oracle specifics ... generally, model follows:

create multiple database users, each different levels of database access, depending on role. these db users not correspond actual users, instead correspond roles, 4: total access create/drop/update tables etc., write access update tables, read access select tables, execute stored procedures , functions.

for type of modification info asp.net app requires, encapsulate operation in stored procedure. write data-access interface @ stored procedure level.

create "stored_procedure_executor" db user, access permits executing stored procedures (and functions). user not have access create/drop/update/select straight tables.

in asp.net application, need store/provide connection string (db user login information) "stored_procedure_executor" db account.

during development, maintenance, back upwards need ability create/drop/update/select directly, , can create additional db users appropriate level of access. utilize these db accounts db management tools, not via asp.net. thus, login info never need exposed @ asp.net level.

this guided security concerns, can improve performance forces think way/patterns in info accessed, , allows optimize both construction of database, implementation of most-often used queries (embedded in stored procedures).

oracle multiple-users