My server is part of a W2K domain. What do you advice me as account to
run my SQL*Server, service started with a domain user account or as
local system ?
I need advices from a security point of view.
Thank's in advanceDepends on your requirements...
First, I would personally never recommend running SQL in a production
environment as Local System.
If the SQL proccess will ever need to connect to file shares on other
machines (like to backup data to remote location etc...) then you can either
use a domain account, or use local accounts with matching usernames and
passwords on the SQL server and any machine it may connect to.
If your SQL proccess will never connect to File shares, or similar resources
on the network, then you should run it with a Local User account on the box.
But of course, this is just my opinion.
GL
"Kona" <kona_iron@.yahoo.fr> wrote in message
news:a1de658a.0404191607.75ec6a49@.posting.google.c om...
> Hello,
> My server is part of a W2K domain. What do you advice me as account to
> run my SQL*Server, service started with a domain user account or as
> local system ?
> I need advices from a security point of view.
> Thank's in advance|||Thank you for your opinion.
And I also agree to not use Local System, all the more since this
account as network access into the same W2K domain (that was not the
case under NT).
"GL" <GL@.noSpam.ReplyToNewsgroup.com> wrote in message news:<108ddd45gbs8k69@.news.supernews.com>...
> Depends on your requirements...
> First, I would personally never recommend running SQL in a production
> environment as Local System.
> If the SQL proccess will ever need to connect to file shares on other
> machines (like to backup data to remote location etc...) then you can either
> use a domain account, or use local accounts with matching usernames and
> passwords on the SQL server and any machine it may connect to.
> If your SQL proccess will never connect to File shares, or similar resources
> on the network, then you should run it with a Local User account on the box.
> But of course, this is just my opinion.
> GL
> "Kona" <kona_iron@.yahoo.fr> wrote in message
> news:a1de658a.0404191607.75ec6a49@.posting.google.c om...
> > Hello,
> > My server is part of a W2K domain. What do you advice me as account to
> > run my SQL*Server, service started with a domain user account or as
> > local system ?
> > I need advices from a security point of view.
> > Thank's in advance|||Depends on your requirements...
First, I would personally never recommend running SQL in a production
environment as Local System.
If the SQL proccess will ever need to connect to file shares on other
machines (like to backup data to remote location etc...) then you can either
use a domain account, or use local accounts with matching usernames and
passwords on the SQL server and any machine it may connect to.
If your SQL proccess will never connect to File shares, or similar resources
on the network, then you should run it with a Local User account on the box.
But of course, this is just my opinion.
GL
"Kona" <kona_iron@.yahoo.fr> wrote in message
news:a1de658a.0404191607.75ec6a49@.posting.google.c om...
> Hello,
> My server is part of a W2K domain. What do you advice me as account to
> run my SQL*Server, service started with a domain user account or as
> local system ?
> I need advices from a security point of view.
> Thank's in advance|||Thank you for your opinion.
And I also agree to not use Local System, all the more since this
account as network access into the same W2K domain (that was not the
case under NT).
"GL" <GL@.noSpam.ReplyToNewsgroup.com> wrote in message news:<108ddd45gbs8k69@.news.supernews.com>...
> Depends on your requirements...
> First, I would personally never recommend running SQL in a production
> environment as Local System.
> If the SQL proccess will ever need to connect to file shares on other
> machines (like to backup data to remote location etc...) then you can either
> use a domain account, or use local accounts with matching usernames and
> passwords on the SQL server and any machine it may connect to.
> If your SQL proccess will never connect to File shares, or similar resources
> on the network, then you should run it with a Local User account on the box.
> But of course, this is just my opinion.
> GL
> "Kona" <kona_iron@.yahoo.fr> wrote in message
> news:a1de658a.0404191607.75ec6a49@.posting.google.c om...
> > Hello,
> > My server is part of a W2K domain. What do you advice me as account to
> > run my SQL*Server, service started with a domain user account or as
> > local system ?
> > I need advices from a security point of view.
> > Thank's in advance
No comments:
Post a Comment