msqldba,
No there is no problem in making NT Authority/System login have sysadmin
privileges, in fact it is required if you have removed the
BUILTIN\Administrators login as the external MSSearch services needs
sysadmin privileges to access SQL Server. Note, this is by design. You can
implement this via the following T-SQL code:
exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System','us_english'
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
Additionally, see KB article Q263712 "INF: How To Prevent Windows NT
Administrators From Administering a Clustered SQL Server" at
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q263712 as this KB
article recommends: "If a full-text search will be used on the cluster, you
must add the [NT Authority\System] account to the server's "sysadmin"
group."
Regards,
John
--
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/ [quoted text, click to view] "msqldba m via SQLMonster.com" <forum@SQLMonster.com> wrote in message
news:5116CE83ADBA0@SQLMonster.com...
> Hilary,
>
> So there are no problems in making NT Authority/System a sysadmin(SA) in
sql
> server
>
> Thanks,
>
>
> Hilary Cotter wrote:
> >No, basically the reason dba's remove the builtin\admin account is to
ensure
> >that NT admin's are automatically system admins on the SQL Server box. NT
> >Authority/System merely gives the system account rights to SQL Server
which
> >MSSearch requires to contact SQL Server and vice versa. With NT
> >Authority/System the NT admin's can no longer automatically administer
your
> >SQL Server.
> >
> >> Hello,
> >>
> >[quoted text clipped - 6 lines]
> >>
> >> Thanks In Advance!
>
>
> --
> Message posted via SQLMonster.com
>
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-search/200507/1