Re: SQL Set to System Account - Sharepoint Question

Thanks Tony,

That gives me a little more clarity and a better idea of what I need to ask
the software vendor.

I hadn't though to creating a new instance. If they do need to run on the SA
account, that's exactly what I'll do.

Lesa

"Tony Su" <TonySu@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:471BCFA7-32F9-49FD-906F-2167B1000D22@xxxxxxxxxxxxxxxx
> Lesa,
> Although Lee has attempted to answer your question, I hope he won't mind
if
> I respond differently.
>
> First, I doubt you are asking your question correctly... I'm pretty sure
> you're referring to the SA (which generally is said to stand for "SQL
> Administration", not System Account) account.
>
> The app may or may not have reasons to at least run with SA
permissions...,
> generally to initially create a database and the supporting database
> structures outside of the database itself.
>
> But, if the app installation doesn't need to do that initially and
> <definitely> after the installation there isn't normally any reason to
> continue to run using SA permissions.
>
> My recommendation:
> If you must grant SA permissions, install a completely separate instance
of
> SQL, don't use an instance being used for anything else.
> <Ask> the App Support people why SA is required. If it's needed for
> installation, ask them if the app will run using a non-SA account
thereafter,
> even if the accounts needs to be assigned the dbo role (which essentially
> gives it super user permissions but only within the database).
>
> As for conflicts with MSDE and a later upgrade to SQL, if you keep the new
> application's database completely separate offhand I don't see how you
will
> run into any kind of problem. If you decide to use the same SQL instance
for
> an SBS app and your new app, although not a critical step I'd generally
> recommend upgrading first to make life easier for yourself.
>
> HTH,
> Tony
>
>
>
>
>
>
> ""Lee Li[MSFT]"" wrote:
>
> > Dear Lesa,
> >
> > Thank you for posting.
> >
> > This is Lee and I am glad to meet you in the newsgroup again.
> > You will NOT get any problems if you set the SQL server to be started at
> > the System Account.
> > After you had installed the SBS 2003 on the computer, a MSDE will be
> > installed on the computer automatically.
> > The MSDE is a simple version of SQL server and is used by the
Sharepoint.
> > By default, the MSDE service is started in the System Account.
> > So it will be no problem for you to move the sharepoint DB to the SQL
> > server installed on this computer which was started at the System
Account.
> >
> > By the way, for detail steps to move the sharepoint DB, please take a
look
> > at the following URL:
> >
http://download.microsoft.com/download/1/1/6/11671e4d-fb21-489c-870f-db36fd2
> > 1a7d2/SBS_MoveDataFolders.DOC
> >
> > Hope the above information helps. Have a nice day!
> >
> > Sincerely,
> >
> > Lee Li
> > Microsoft Online Partner Support
> >
> > When responding to posts, please "Reply to Group" via your newsreader so
> > that others may learn and benefit from your issue.
> > =====================================================
> > Business-Critical Phone Support (BCPS) provides you with technical phone
> > support at no charge during critical LAN outages or "business down"
> > situations. This benefit is available 24 hours a day, 7 days a week to
all
> > Microsoft technology partners in the United States and Canada.
> >
> > This and other support options are available here:
> > BCPS:
> >
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
> > Others:
https://partner.microsoft.com/US/technicalsupport/supportoverview/
> >
> > If you are outside the United States, please visit our International
> > Support page:
> > http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
> >
> > =====================================================
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >


.

Relevant Pages

  • RE: SQL Set to System Account - Sharepoint Question
    ... Administration", not System Account) account. ... after the installation there isn't normally any reason to ... SQL, don't use an instance being used for anything else. ... the App Support people why SA is required. ...
    (microsoft.public.windows.server.sbs)
  • Re: SQLSetup0001_xxxxxx_Core(Local).log
    ... Windows Error Text: User cancelled installation. ... Source File Name: datastore\cachedpropertycollection.cpp ... SQL Server 2005 Setup requires administrator permissions on every ... update permissions for the account ...
    (microsoft.public.sqlserver.clustering)
  • Re: Problem: SQL Server 2005 Setup requires administrator permissions on every cluster node
    ... Windows Error Text: User cancelled installation. ... Source File Name: datastore\cachedpropertycollection.cpp ... SQL Server 2005 Setup requires administrator permissions on every ... update permissions for the account ...
    (microsoft.public.sqlserver.clustering)
  • Re: Service Pack 2 Installation Error
    ... This is a clustered installation though I'm not sure my problem is cluster related, so I hope I posted in the right place. ... I started to install SQL Server 2005 SP2. ... I've tried the domain admin account as well as all of the other accounts that are even possibly the correct one, but each time I try, I'm given an error that says. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Failed to modify security permissions on WMI namespace
    ... The account you logged in as has administrator privileges on both nodes. ... AD or the installation account has permission to create them during the ... Here I enclosed a piece of my failed SQL 2005 installation. ... SQL Server Setup failed to modify security permissions on WMI ...
    (microsoft.public.sqlserver.clustering)