Join me at Google+ ...

This article is a part of a series describing the installation of Microsoft Office SharePoint Server 2007 (MOSS) on a Windows Server 2008 with the newly released SQL Server 2008. SharePoint 2007 relies on a database server and that will be SQL Server 2005 or SQL Server 2008.

Update: 60 min - Install SharePoint with PowerShell easy and fast

Back with SharePoint 2007 you had the choice between a 32bit and 64bit SharePoint 2007 deployment. I suggest you just take the 64bit pieces of Windows Server 2008, SQL Server 2005 or 2008 and SharePoint 2007. Hyper-V allows you to virtualize 64bit environments compared to Virtual PC or Virtual Server 2005 which didn't allow that. Hyper-V is really fast so you shouldn't consider using the older technologies... it saves you tons of time.

If you go a step back to the previous articles there are two accounts needed here: the SQL Server service account and the setup administrator. The SQL Server service account is a domain account used to run the SQL Server service instance. The setup administrator is the install account for SharePoint 2007 but will be used here also as the SQL Server administrator (sysadmin). This way you need only the setup administrator to manage Windows Server, SQL Server and SharePoint 2007.

It's just to simplify things...

Please have a look at:

Installation

Start the "setup.exe" of your SQL Server 2008 installation DVD.
You are prompted to install the .NET Framework 3.5 SP1 (surprise since this was officially released later)
After that you need to install a Windows Update.

Start the setup.exe.

Istall the .NET Framework 3.5 SP1. Install a Windows Update.

On the left side click "Installation" and on the right side click "New SQL Server stand-alone installation or add features to an existing installation".
After that select your version of SQL Server 2008.

Select New SQL Server stand-alone installation or add features to an existing installation Select your version of SQL Server 2008.

After installing the setup support files you are prompted that there are some warnings. You can ignore that on a development environment.

Install the setup support files. Ignore the warnings on a development environment.

After that select the "Database Engine Services" feature and the "Management Tools" feature.
Keep the default instance checked.

Select the Database Engine Services feature and the Management Tools feature. Keep the default instance checked.

After validating the hard disk requirements you have to select a services account.

Please use the domain account from Part 3: Domain Accounts.

After validating the hard disk requirements you have to select a services account. Select the SQLservice account.

You don't need to change the collation settings given by the installation wizard.
Use "Windows Authentication" and add the current user as a SQL Server administrator.

Dont change the collation settings. Use Windows Authentication and add the current user as a SQL Server administrator.

Click a few times next to start installation.

Click to start installation. The installation was successful dialog shown at the end.

Configuration

You have to enable "named pipes".
"Remember to reboot for the named pipes to be available (needed for part 6)." (Updated 13. September 2009, provided by Audun)

You have to enable named pipes.

"Remember to go back to the Domain setup page and set the required permissions for SQL server /setupAdmin account." - Installing MOSS 2007 on Windows Server 2008 and SQL Server 2008 - Part 3: Domain Accounts (Updated 13. September 2009, provided by Audun)



Get updates

 

Comments (14) -

10/27/2008 10:55:15 PM #

Andreas - I've been looking for blogs/references that speak to how stable SQL 2008 RTM is proving to be and, in particular, with MOSS 2007.  Was wondering if you have experience with production environments and any feedback with regards to stability/reliability.
Moe

Moe Oro United States Reply

10/29/2008 9:08:36 AM #

Hi,

yes that's a question I have asked myself. I haven't seen any SQL Server 2008 in a production environment right now. The customers I talk to still use SQL Server 2005 and the customers who are going to use SharePoint 2007 need to set up the production environment.

Unfortunately I have to wait until I hear some experiences from the real world..

Andreas

aglaser Switzerland Reply

9/4/2009 10:49:24 AM #

Hi,
Thanks for an excellent guide.
On this page I have two suggestions for improvement, it would be great if you added them.  
Number 1:  Bullet point after configuring named pipes: Remember to reboot for the named pipes to be available (needed for part 6).
Number 2: Remember to go back to the Domain setup page and set the required permissions for SQL server /setupAdmin account (this step is just sooo easily forgotten).

Audun Norway Reply

9/13/2009 7:30:28 PM #

Hi Audun,

thank you very much! Smile I highly appreciate your suggestions and added them above.

Andreas

Andreas Glaser Switzerland Reply

10/8/2009 9:41:38 PM #

Did you have any issues joining the MOSS VM to the newly created domain?

ehaze United States Reply

10/9/2009 7:00:19 PM #

Hi,

I didn't have any issues... I joined the domain before I installed Active Directory, SQL Server and SharePoint.

Andreas

Andreas Glaser Switzerland Reply

10/11/2009 4:08:41 PM #

I found my issue(s), sort of, I was trying to do this with VWware Workstation....
Once I activated HyperV, things went much smoother.  Thanks for the great blog post!

ehaze United States Reply

10/13/2009 1:34:11 AM #

Wow nice post! These are pretty much the steps I used to successfully install SQL server 2008 in our medium sized MOSS farm.

If anyone is interested I have also detailed a process for migrating from SQL server 2005 to SQL server 2008 (on Windows Server 2008) within a live SharePoint 2007 farm. Feel free to check it out over at http://mossblogger.blogspot.com/ if you are interested.

Cheers, Ben.

Benjamin Athawes United Kingdom Reply

10/13/2009 10:38:42 AM #

@ehaze / @Benjamin

Thanks for sharing the information with us.

Andreas Glaser Switzerland Reply

11/5/2009 12:58:49 PM #

Hi,

Thanks for this excellent tutorial...

Naveen India Reply

11/10/2009 9:53:59 AM #

Hi Andreas. Great articles. I have used them as reference for setup in both development environment and production. I have used Windows Server 2008 R2 as base. The only difference I can think of, is that you have to install SP1 on SQL Server 2008.

Ole Kristian Norway Reply

12/3/2009 5:58:42 PM #

Andreas and Moe,
What a great article and discussion!
I've worked with SQL Server 2008 and SharePoint for a couple years and I have seen examples where it is used in stable production sites. If you are starting from scratch, I would definitely recommned considering using the latest platform. However even for SharePoint 2010, SQL 2005 is still supported, but you must use the latest service pack and the 64bit version.
Tom

Tom Resing United States Reply

12/6/2009 8:27:07 PM #

@Tom: Thanks for your input Smile

Andreas Glaser Switzerland Reply

3/23/2010 11:56:11 PM #

Hi Andreas, do you know (or can point me to where it is) which are the permission that are needed for the account in SQL Server where you are using remote SQL (MOSS Server and SQL Server are different machines).

Gilberto Mexico Reply

Pingbacks and trackbacks (1)+

Add comment




  Country flag
biuquote
Loading