Re: SQL 2000 installation advice needed

Thank you for your reply.

Regarding the "named pipes" option. Is there any reason I should not select
this option when installing SQL Server?



"Jens Süßmeyer" wrote:

> > Warning: beginner here.
>
> Welcome. ;-)
>
> Is there any **compelling** reason I should not use the Win2k3
> > Administrator account?
>
> If you mean with that the local administrator account, there might be some
> reason not to choose this, instead of choosing a domain accounts. Domain
> Accounts can be granted extended access to network ressource (as long as you
> will need them) e.g. Mail access, file share access etc. By using a "login
> as a service" account the security is improced because of having a
> privileged user who won´t be able to logon interactively at workstations. As
> far as you won´t need any permissions in your network or other ressources,
> you can head for the network service account or the local system account.
>
>
> Security is not very important to me. I have
> > Ghost backups of the operating system, and will backup the database daily.
> > I
> > can restore the operating system in a few minutes.
>
> Thats nothing about security as the meaning I have of it. So your data will
> be restored quickly in the case of any data loss, but the planning of
> security should be done even if you got an internal low priority app or a
> productional OLTP system. (my two pence, perhaps it´s the schizophrenic part
> in me :-))
>
> > Another question: during installation of SQL Server 2000 it asks
> > something
> > about using "named pipes". Not having a clue what "named pipes" are I
> > always
> > select the default. Is there anything wrong with that?
>
>
> http://www.linktionary.com/n/named_pipes.html
>
> HTH, Jens Suessmeyer.
>
> ---
> http://www.sqlserver2005.de
> ---
>
>
>
>
> "kvr901" <kvr901@xxxxxxxxxxxxxxxxxxxxxxxxx> schrieb im Newsbeitrag
> news:CD307AC4-72CD-4D41-9EE0-7DE7E7495939@xxxxxxxxxxxxxxxx
> > Warning: beginner here.
> >
> > I have installed SQL Server 2000 Enterprise on my Win2003Server box
> > several
> > times (each time using a clean installation of Win2k3), and not had any
> > problems. I can use the database fine both directly from other computers
> > and
> > through a small ASP.NET web application.
> >
> > The beginners book I am using "Microsoft SQL Server 2000 for Dummies"
> > suggests using a "Domain User Account". It goes on to say the account
> > should
> > be a member of the Administrators group, password never expires, log on as
> > service rights.
> >
> > So far I have been creating a user with those attributes, but I am
> > wondering.... Is there any **compelling** reason I should not use the
> > Win2k3
> > Administrator account? It would make my life simpler to not have to
> > document
> > another user and password. Security is not very important to me. I have
> > Ghost backups of the operating system, and will backup the database daily.
> > I
> > can restore the operating system in a few minutes.
> >
> > After a while I will eventually use SQL Server for a small web
> > application.
> > The Win2k3 server will not be used for anything else. The server machine
> > is
> > not used for anything on my small network. All use will be for incoming
> > internet access to the small ASP.NET application I am building.
> >
> >
> > Another question: during installation of SQL Server 2000 it asks
> > something
> > about using "named pipes". Not having a clue what "named pipes" are I
> > always
> > select the default. Is there anything wrong with that?
> >
> > TIA
> >
> >
>
>
>
.

Relevant Pages

  • Re: SMS_MP_Control_Manager Errors
    ... A colleage of mine figure it out, it was "local security policy" problem, he ... IUSR_"Computer account" must be able to access the computer from the network. ... delete the Guests group from it. ... Verify that the SQL server is properly configured to ...
    (microsoft.public.sms.admin)
  • Http verification .sms_aut (port 80) failed
    ... I noticed I couldn't get SMS reports to work.... ... MP encountered an error when connecting to SQL Server. ... If using a standard SQL security account, ...
    (microsoft.public.sms.admin)
  • Re: Http verification .sms_aut (port 80) failed
    ... I resolved a problem like this changing the Security settings on SMS_MP ... I had to go into SQL Server Configuration Manager / SQL Server 2005 Network ... I noticed I couldn't get SMS reports to work.... ... If using a standard SQL security account, ...
    (microsoft.public.sms.admin)
  • Re: SQL 2000 installation advice needed
    ... >> If you mean with that the local administrator account, ... >> Security is not very important to me. ... >>> Ghost backups of the operating system, ... >>> can restore the operating system in a few minutes. ...
    (microsoft.public.sqlserver.setup)
  • Re: Switching to Advanced Security
    ... None of the patching tools have been implemented, ... that time with the option to switch to Advanced Security, ... siteservermachinename$ account in AD to the Systems Managment container ... local SQL Server security, in that the local computer account has ...
    (microsoft.public.sms.setup)
Loading