Re: master db

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


"Hari Prasad" <hari_prasad_k@xxxxxxxxxxx> wrote in message
news:%23jX0Tz%23WFHA.3140@xxxxxxxxxxxxxxxxxxxxxxx
> Yes, you are correct.
>
> Thanks
> Hari
>
> "Joh" <joh@xxxxxxxxxxxx> wrote in message
> news:e8Yi%23k%23WFHA.2520@xxxxxxxxxxxxxxxxxxxxxxx
>> You mean i have to create one table and put all the users in the table
>> and
>> application hit that table right...
>>
>> "Hari Prasad" <hari_prasad_k@xxxxxxxxxxx> wrote in message
>> news:O74pHf#WFHA.2448@xxxxxxxxxxxxxxxxxxxxxxx
>>> 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
>>>
>>> "Joh" <joh@xxxxxxxxxxxx> wrote in message
>>> news:uvbyyU%23WFHA.1152@xxxxxxxxxxxxxxxxxxxxxxx
>>> > 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.
>>> >
>>> >
>>> >
>>> > "Hari Prasad" <hari_prasad_k@xxxxxxxxxxx> wrote in message
>>> > news:OYrFU49WFHA.3176@xxxxxxxxxxxxxxxxxxxxxxx
>>> >> 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
>>> >>
>>> >> "Joh" <joh@xxxxxxxxxxxx> wrote in message
>>> >> news:usHtbi9WFHA.2664@xxxxxxxxxxxxxxxxxxxxxxx
>>> >> > 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@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
>>> >> > wrote
>>> >> > in
>>> >> > message news:uZmH2d9WFHA.2124@xxxxxxxxxxxxxxxxxxxxxxx
>>> >> >> 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@xxxxxxxxxxxx> schrieb im Newsbeitrag
>>> >> >> news:eJiTYc9WFHA.3348@xxxxxxxxxxxxxxxxxxxxxxx
>>> >> >> > if we create 1000 database users then is this create adverse
>> effect
>>> > on
>>> >> > the
>>> >> >> > master database?
>>> >> >> >
>>> >> >> > Thanks
>>> >> >> >
>>> >> >> >
>>> >> >>
>>> >> >>
>>> >> >
>>> >> >
>>> >>
>>> >>
>>> >
>>> >
>>>
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: Single Sign on
    ... > do is create an NT global group that contains your user accounts. ... > group appropriate permissions in SQL Server and appropriate permissions to ... This is SQL Server Windows Authentication model and only ...
    (microsoft.public.sqlserver.setup)
  • Re: Locking down database accounts
    ... Windows Authentication rather than SQL Server user accounts and passwords. ...
    (microsoft.public.sqlserver.security)
  • Re: question ... query and filtering
    ... > If the data is stored on SQL Server you can create user accounts on SQL ... Open Enterprise Manager and look at the Security node under the ... Use database Roles to assign ...
    (microsoft.public.access.queries)
  • Re: ODBC Connection - read/write access
    ... SQL Server will not accept a connection from any API unless that connection ... You have to specifically add logins to SQL Server before other people can ... those user accounts. ...
    (microsoft.public.sqlserver.security)
  • Report stalling when printing
    ... I'm managing a larger print application using Access 2000 and SQL server ... Some time when the system is handling a large amount ...
    (microsoft.public.access.reports)