We help IT Professionals succeed at work.

What is the correct form for SharePoint installation parameters?

Medium Priority
Last Modified: 2012-05-11
What form should I use for the database server name and user name (credentials for farm user account) parameters, when installing SharePoint 2010 (a scripted installation)?

Is it correct that if I have a named instance of SQL I should have the form "serverName\instanceName" for the database server name?  Should I use this form regardless of named/default instance? Maybe the difference is if I use SQL full version or SQL Express when naming this parameter?

If I choosed the default instance (MSSQLSERVER), when installing SQL, isn´t that also a named instance?
I know I should use a named instance if I want to use SQL for other applications besides SharePoint. So then the default instance isn´t a named instance after all? Confusing...

Servername refers to the computername doesn´t it?

What about the user name?

If you have any other remarks on the form for naming the SharePoint installation parameters, please inform me :)

Watch Question

Unlock this solution and get a sample of our free trial.
(No credit card required)

Hi Mick,

 Please check the below msdn link.


Hope it may helpful to you.



bradgcoza; Thank you for the answers - exactly what I was looking for :)

When I installed SQL Server 2008, I used the same credential for all services/accounts, the same one I have for Windows Server - an administrator user account. That account should work for SharePoint user credentials then?

The account will work but I would strongly recommened making a new account for the SharePoint Farm account and giving it the above mentioned permissions in SQL

Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.