Re: Tutorial/Guide for installing SQL Server2K SP3 on WS03

From: Bryan (Juniper2000_at_hotmail.com)
Date: 09/07/04


Date: Tue, 07 Sep 2004 12:08:20 GMT

I agree with Peter. I always install with mixed mode. I depend on the
Windows Authentication for the most part because of easier user management,
however, there are many cases where a SQL login may be needed. Such cases
would be external users like contractors that need temporary privileges but
are not part of your domain, or setting up a SQL login for certain linked
servers to use that are not part of the domain.

-- 
Bryan Bitzer MCP
Senior Database Administrator
Marshall & Swift / Boeckh
www.msbinfo.com
"Peter The Spate" <anonymous@discussions.microsoft.com> wrote in message
news:733a01c494c8$c395f010$a601280a@phx.gbl...
> When intalling SQL Server go for mixed.
>
> The sa user is an important one however its a user id
> rather than an NT ID.
>
> The Authenticated ones are really cool as anyone who can
> log on to NT can then (if you allow them) access to SQL
> Server.
>
> With the authenticity you can also put in NT User Groups,
> i.e. say 10 administration staff, and them assign them
> permissions.
>
> Personally then I would say Authenticated users for day to
> day stuff, but keep the sa password for 'just in case'
> scenarios.
>
> Peter
>
> "It's true hard work never killed anybody, but I figure,
> why take the chance?"
> Ronald Reagan
>
>
>
> >-----Original Message-----
> >> I would first think about how the database server will
> be used and
> >what\who
> >> will be connecting to it. There are a lot of things to
> consider in
> >> performance and hardware as well. If you did not
> install SQL Server yet
> >then
> >> you would not have BOL.
> >> Try visiting
> >>
> http://www.microsoft.com/sql/techinfo/productdoc/2000/defau
> lt.asp
> >> to download BOL
> >
> >Great - that helps.  But since this is a sandbox install,
> I just went for
> >it.  Compared to installing Oracle 9i on Solaris, it was
> a breeze.  I just
> >took all the defaults.  One thing that I was unsure of
> was which
> >authentication to use: Windows or SQL server.  In the
> real world, what is
> >best practice?
> >
> >
> >.
> >


Relevant Pages

  • Re: Problem of MSDE 2000 Release A Installation
    ... > System Prompt msg "pls go to control panel to install &configure your sys ... >> talk to SQL Server. ... >> Authentication, the new default, lets anyone with a Windows login talk to ...
    (microsoft.public.sqlserver.msde)
  • Re: Administering MSDE with Enterprise Manager
    ... SETUP SAPWD="wombat" created 'Windows Only Authentication'. ... the MSDE machine from those on the machine that I was connecting from. ... > A. You can only use SQL Server tools and services in conjunction ... >> created during MSDE's install. ...
    (microsoft.public.sqlserver.connect)
  • Re: Administering MSDE with Enterprise Manager
    ... SETUP SAPWD="wombat" created 'Windows Only Authentication'. ... the MSDE machine from those on the machine that I was connecting from. ... > A. You can only use SQL Server tools and services in conjunction ... >> created during MSDE's install. ...
    (microsoft.public.sqlserver.msde)
  • Re: Administering MSDE with Enterprise Manager
    ... SETUP SAPWD="wombat" created 'Windows Only Authentication'. ... the MSDE machine from those on the machine that I was connecting from. ... > A. You can only use SQL Server tools and services in conjunction ... >> created during MSDE's install. ...
    (microsoft.public.sqlserver.setup)
  • Re: Login failed for user (null). Reason: Not associated with a trusted SQL Server connection
    ... Peter ... > On the SQL Server Security tab, configure SQL Server to use "SQL Server ... > Windows" authentication. ...
    (microsoft.public.sqlserver.server)