Groups | Blog | Home
all groups > sql server clients > may 2005 >

sql server clients : master db


Joh
5/18/2005 2:27:08 PM
if we create 1000 database users then is this create adverse effect on the
master database?

Thanks

Joh
5/18/2005 2:37:55 PM
You mean there is no harm in creating the database users.... or we have to
save all the users in the table and check their credential from there...

Thanks

"Jens Süßmeyer" <Jens@Remove_this_For_Contacting.sqlserver2005.de> wrote in
message news:uZmH2d9WFHA.2124@TK2MSFTNGP14.phx.gbl...
[quoted text, click to view]

Joh
5/18/2005 4:06:04 PM
here I am talking about application users.

[quoted text, click to view]

Joh
5/18/2005 4:07:58 PM
Over here is a call centre and when any new guys come to use application
they have created the database user for that.... this is totally wrong.



[quoted text, click to view]

Joh
5/18/2005 4:37:04 PM
You mean i have to create one table and put all the users in the table and
application hit that table right...

[quoted text, click to view]

Jens Süßmeyer
5/18/2005 8:29:06 PM
Database users or only stored in the database, referenced to the server
users on server level.

--
HTH, Jens Suessmeyer.

---
http://www.sqlserver2005.de
---
"Joh" <joh@mailcity.com> schrieb im Newsbeitrag
news:eJiTYc9WFHA.3348@TK2MSFTNGP14.phx.gbl...
[quoted text, click to view]

Jens Süßmeyer
5/18/2005 8:38:31 PM
Sorry some part missing of the answer... No, as of many hundred users there
is no feelable difference between a singleuser database to that one.


"Jens Süßmeyer" <Jens@Remove_this_For_Contacting.sqlserver2005.de> schrieb
im Newsbeitrag news:uZmH2d9WFHA.2124@TK2MSFTNGP14.phx.gbl...
[quoted text, click to view]

Hari Prasad
5/19/2005 12:47:41 AM
Hi,

There is no harm in creating more database users.

we have to save all the users in the table and check their credential from
there...???

It is always better to create SQL Server Logins (secured) rather than
storing users in normal user tables.

Thanks
Hari
SQL Server MVP

[quoted text, click to view]

Hari Prasad
5/19/2005 1:57:07 AM
Hi,

In this case you can have a common database user and keep a application
table to hold all the application users.

Thanks
Hari
SQL Server Mvp

[quoted text, click to view]

Hari Prasad
5/19/2005 2:33:15 AM
Yes, you are correct.

Thanks
Hari

[quoted text, click to view]

Joe Yong
5/20/2005 2:49:57 PM
This means you are managing user accounts within the application instead of
managing them via SQL Server.

There are pros and cons to both but IMHO, the pros of managing the users in
SQL Server or Windows (use integrated security) far outweigh the cons.
Issues like accountability, security management and isolation, movement,
etc... are all built into SQL Server and/or Windows whereas if you manage
user account info manually, you have to write and maintain code to do that.
It can certainly be done and most "older" apps do exactly that but the
justifications for doing so get fewer and weaker with every iteration of the
products.


joe


[quoted text, click to view]

AddThis Social Bookmark Button