Login user name

Hi,
can it be a problem for SQL if I have 41 users using the same logging name ?
txhi
No as far it is not a admin account.
from
DOller|||Technically it should work. In reality you've lost all control. What
happens if you decide to disable one user account? You will disable all 41
users. What if you want 5 users to have access to a new database, but not
the other users? You're giving an all-or-none proposition here. Or if
someone logs into your database when they're not supposed to, or does
something verboten while in there? Well, you can narrow the problem down to
41 people. How do you handle that? Fire them all?
It's better to give each user his/her own login. Look into Windows
Authenticated security in BOL.
"ms" <nowayyyy@.nospammmm.fr> wrote in message
news:ufUia5MuFHA.2540@.TK2MSFTNGP09.phx.gbl...
> Hi,
>
> can it be a problem for SQL if I have 41 users using the same logging name
> ?
> tx
>|||To add to Michael's reply:
Using a Windows Group would be the best case scenario here for account
managment, minimizing the number of total logins and the ability to
determine the Windows User name for the user in the Windows Group using
SUSER_SNAME().
HTH
Jerry
"Michael C#" <xyz@.abcdef.com> wrote in message
news:%OLVe.372$gE7.314@.fe08.lga...
> Technically it should work. In reality you've lost all control. What
> happens if you decide to disable one user account? You will disable all
> 41 users. What if you want 5 users to have access to a new database, but
> not the other users? You're giving an all-or-none proposition here. Or
> if someone logs into your database when they're not supposed to, or does
> something verboten while in there? Well, you can narrow the problem down
> to 41 people. How do you handle that? Fire them all?
> It's better to give each user his/her own login. Look into Windows
> Authenticated security in BOL.
> "ms" <nowayyyy@.nospammmm.fr> wrote in message
> news:ufUia5MuFHA.2540@.TK2MSFTNGP09.phx.gbl...
>|||The only reason why they are using their computers is to use the same
database and do exactly the same job (surveyer, only for 2 months). So if
its not a problem for SQL Server, I dont see any reason to create 41 user
names.
tx all
(they already have their own user name in the survey application that
connect to my SQL Server btw, they only use the same logging name for
Windows XP.)|||It's always your choice, but when management wants to know who did what in
your database; or wants a certain user locked out, what are you going to
tell them? "I have it narrowed down to one of 41 people?" Or "I can't lock
one person out without locking them all out".
As always, how you manage - or mis-manage - your SQL Server is completely up
to you.
Best of luck
"ms" <nowayyyy@.nospammmm.fr> wrote in message
news:O13cSvXuFHA.3500@.TK2MSFTNGP09.phx.gbl...
> The only reason why they are using their computers is to use the same
> database and do exactly the same job (surveyer, only for 2 months). So if
> its not a problem for SQL Server, I dont see any reason to create 41 user
> names.
> tx all
> (they already have their own user name in the survey application that
> connect to my SQL Server btw, they only use the same logging name for
> Windows XP.)
>|||"Michael C#" <xyz@.abcdef.com> a crit dans le message de
news:Fi2Xe.7570$IC3.7538@.fe12.lga...
> It's always your choice, but when management wants to know who did what in
> your database; or wants a certain user locked out, what are you going to
> tell them? "I have it narrowed down to one of 41 people?" Or "I can't
lock
> one person out without locking them all out".
why I would lock someone ? If I dont want him to use the database, its
because he is not working for me anymore. And like I said, the application
connecting to my db is already using 41 different surveyer names.
tx for your infos anyway !|||No problem. Those were just a couple of examples. As long as you're aware
that situations do pop up now and then where the granularity of your
security can be very important.
"ms" <nowayyyy@.nospammmm.fr> wrote in message
news:ePNZpjJvFHA.2008@.TK2MSFTNGP10.phx.gbl...
> "Michael C#" <xyz@.abcdef.com> a crit dans le message de
> news:Fi2Xe.7570$IC3.7538@.fe12.lga...
> lock
> why I would lock someone ? If I dont want him to use the database, its
> because he is not working for me anymore. And like I said, the application
> connecting to my db is already using 41 different surveyer names.
> tx for your infos anyway !
>