Step 1 - SQL Server 2008 Installation and Configuration
Introduction
This post is the first of a group showing how to use SQL Server 2008 Reporting Services with SharePoint 2007.
The next steps are:
The goal is to quickly allow someone to create reports and to discover SharePoint Integrated Mode features: deployment, Web Parts dashboards, subscription, snapshotings, etc..
Even planning for further deployments in a Farm environment with several servers and Active Directory, it may be usefull to have been familiarized with involved products installation, configuration and use, by having tested it in a Simple Farm Topology with one computer and local accounts.
For the current step, you can refer to this MSDN article: How to: Install SQL Server 2008 (Setup)
This installation is compliant with both MOSS 2007 and Windows SharePoint Services.
The next steps are:
- Step 2 - Windows SharePoint Services 3.0 Installation and Configuration
- Step 3 - Configuring Reporting Services for SharePoint 3.0 Integration - Part 1 : Operations performed with Reporting Services Configuration tool
- Step 4 - Configuring Reporting Services for SharePoint 3.0 Integration - Part 2: Operations performed in SharePoint Central Administration (includes Microsoft SQL Server 2008 Reporting Services Add-in for Microsoft SharePoint Technologies Installation)
- Step 5 - Sample Databases for Microsoft SQL Server 2008 Installation
- Step 6 - Report Creation and Deployment in SharePoint 2007 with Business Intelligence Development Studio (BIDS)
The goal is to quickly allow someone to create reports and to discover SharePoint Integrated Mode features: deployment, Web Parts dashboards, subscription, snapshotings, etc..
Even planning for further deployments in a Farm environment with several servers and Active Directory, it may be usefull to have been familiarized with involved products installation, configuration and use, by having tested it in a Simple Farm Topology with one computer and local accounts.
For the current step, you can refer to this MSDN article: How to: Install SQL Server 2008 (Setup)
This installation is compliant with both MOSS 2007 and Windows SharePoint Services.
1 - Prerequisites
- Be sure to have Windows 2003 Server with SP2 before starting installation.
2 - Installation Overview
This installation includes the following steps:
- Step 1: Launching Installation
- Step 2: prerequisites Installation dialog box
- Step 3: Net Framework 3.5 + SP1 Installation
- Step 4: Windows Installer 4.5 Installation
- Step 5: Launching a new installation of SQL Server 2008
- Step 6: Passing System Configuration Checker
- Step 7: Choosing a free SQL Version, or entering product key
- Step 8: SQL Server prerequisites Installation Wizard
- Step 9: Passing System Configuration Checker
- Step 10: Selecting Installation features
- Step 11: Instance Configuration Page
- Step 12: Disk Space Requirements Page
- Step 13: Server Configuration
- Step 14: DataBase Engine Collation
- Step 15: Database Engine Configuration - Account Provisioning page
- Step 16: Reporting Services Configuration page
- Step 17: Error and Usage Reporting
- Step 18: Passing System Configuration Checker
- Step 19: Ready to install page - Installation Progress
- Step 20: Closing Installation
- Step 21: Checking Installation: Opening SQL Server 2008 Management Studio
- Step 22: Configure your new SQL Server installation
3 - Installation
3.1 Step 1: Launching Installation
Double click the "setup.exe" of your SQL Server 2008 installation media.
3.2 Step 2: prerequisites Installation dialog box
If the prerequisites Installation dialog box appears, click OK.
3.3 Step 3: Net Framework 3.5 + SP1 Installation
If the 3.5 SP1 installation dialog box appears, select the radio button to accept the .NET Framework 3.5 SP1 License Agreement. Click Install.
You may wait from 5 to 20 minutes depending on your system hardware configuration.
When installation of .NET Framework 3.5 SP1 is complete, click Exit.
3.4 Step 4: Windows Installer 4.5 Installation
Windows Installer 4.5 is also required, and might be installed by the Installation Wizard.
If you are prompted to restart your computer, restart it, and then restart SQL Server 2008 setup.exe.
3.5 Step 5: Launching a new installation of SQL Server 2008
When the prerequisites are installed, the Installation Wizard will run the SQL Server Installation Center. To create a new installation of SQL Server 2008, click New Installation or Add Features to an Existing Installation.
3.6 Step 6: Passing System Configuration Checker
The System Configuration Checker will run a discovery operation on your computer. To continue, click OK. Setup log files are created for your installation. For more information, see How to: View SQL Server Setup Log Files.
3.7 Step 7: Choosing a free SQL Version, or entering product key
On the Product Key page, select an option button to indicate whether you are installing a free edition of SQL Server, or a production version of the product that has a PID key.
On the License Terms page, read the license agreement, and then select the check box to accept the license terms and conditions.
3.8 Step 8: SQL Server prerequisites Installation Wizard 2
The Installation Wizard will install SQL Server prerequisites if they are not already on the computer. These include the following:
- .NET Framework 3.5 SP1
- SQL Server Native Client
- SQL Server Setup Support Files
3.9 Step 9: Passing System Configuration Checker
The System Configuration Checker will verify the system state of your computer before Setup continues.
3.10 Step 10: Selecting Installation features
On the Feature Selection page, we have now to select the components for our installation. A description for each component group appears in the right pane after you select the feature name.
I provide some more information on the current choices:
-
Data Base Engine is obviously mandatory
-
Full text search
I didn't check it because of SharePoint. SharePoint 2007 with SQL Server 2008 configuration doesn't need Full-Text Search feature anymore as it is well explained in MSDN blog:
On the other hand, I plan to install in a further step, SQL Server 2008 database samples (Adventure works), and these samples installation requires Full-Text search feature to be activated.
-
Business Intelligence Development Studio aka BIDS
This is essential regarding Reporting Services integration as it is THE tool that will allow you to create reports and deploy them in SharePoint. For a SQL Server 2008 installation without Reporting Services you can avoid installing this feature.
-
Management-Tools Complete
This feature will install Microsoft SQL Server Management Studio
If you don't need Reporting Services, you can avoid checking complete feature, but the complete one install elements that runs with Reporting Services as noticed in description that appears in the right pane after you select the feature name.
3.11 Step 11: Instance Configuration Page
On the Instance Configuration page, specify whether to install a default instance or a named instance. For a simple farm topology installation on ONE virtual machine, default instance will be enough.
3.12 Step 12: Disk Space Requirements Page
The Disk Space Requirements page calculates the required disk space for the features that you specify. Then it compares the required space to the available disk space. For more information, see Disk Cost Summary.
3.13 Step 13: Server Configuration
On the Server Configuration — Service Accounts page, specify login accounts for SQL Server services. For a simple farm topology installation on ONE virtual machine, I have chosen to use an unique service account that is the Virtual Machine Administrator.
I advise you to configure the SQL Server Agent Service in automatic mode, because it is used by Subscriptions of SQL Server Reporting Services 2008, and doing that, you will not need to start the service manually every time you restart your server.
3.14 Step 14: DataBase Engine Collation Configuration
The SQL Server database collation must be configured for case-insensitive, accent-sensitive, Kana-sensitive, and width-sensitive. This is to ensure file name uniqueness consistent with the Windows operating system as specified this technet article:
3.15 Step 15: Database Engine Configuration - Account Provisioning page
Choose Mixed mode as SharePoint propose in certain screens (Web Application Creation, Search Starting, etc.) to use SQL Authentication.
The two passwords to be typed are for the "sa" login.
3.16 Step 16: Reporting Services Configuration page
We have to select the third option because SharePoint is not installed yet on the virtual machine.
3.17 Step 17: Error and Usage Reporting
On the Error and Usage Reporting page, specify the information that you want to send to Microsoft that will help improve SQL Server. By default, options for error reporting and feature usage are enabled.
3.18 Step 18: Passing System Configuration Checker
The System Configuration Checker will run one more set of rules to validate your computer configuration with the SQL Server features that you have specified.
3.19 Step 19: Ready to install page - Installation Progress
The Ready to Install page shows a tree view of installation options that were specified during Setup. To continue, click Install.
You may wait from 5 to 20 minutes depending on your system hardware configuration.
During installation, the Installation Progress page provides status so that you can monitor installation progress as Setup continues.
3.20 Step 20: Closing Installation
After installation, the Complete page provides a link to the summary log file for the installation and other important notes. To complete the SQL Server installation process, click Close.
3.21 Step 21: Checking Installation: Opening SQL Server 2008 Management Studio
From your machine Start Menu navigate to open SQL Server 2008 Management Studio.
Connect to DataBase Engine
Check it opens properly and contains all usual features.
3.22 Step 22: Configure your new SQL Server installation
As specified in the previously referred article
We have to configure SQL Server in order to prepare SharePoint installation.
As there is a change in the 2008 version of the Configuration Manager, this is the current way to proceed:
On the Start menu, point to All Programs, point to Microsoft SQL Server 2008, point to Configuration Tools, and then click SQL Server Configuration Manager.
Use the SQL Server Network Configuration area to enable connection protocols as follows:
- Named Pipes Enabled
- TCP/IP Enabled
Your SQL Server 2008 installation for Reporting Services Integration with SharePoint 2007 is done.
9 comments:
Great guides, helped a lot and saved a lot of time. Thanks!
Henric
Really nice work ! Thanks a lot for your great job and sharing with us.
Reda
Excellent guide, easy to follow. Thanks for posting it !
Excellent guide.
Slight difference for me as I used it to install SQL Express 2008 SP1 followed by the SQL Server Management Studio.
The steps still work quite intuitively.
Many thanks.
Thanks a lot. This worked pertly fine. I installed SQL Server SP2.
Nice article, very informative.
The only difficulty I have had so far is that you have multiple steps with the same number in your articles. Once I realized that the ones I needed to go through were actually sub-steps, everything made more sense.
This is nice post to guide me to install SQL server 2008 r2...with out any cofusion..as I am in process to install Sharepoint 2010.Thanks!
Sumeet
Thank you for this! and I'm sorry for this question but how come I don't have the other features when I install SQL server 2008? Am I missing something? I just have the management tools.
thanks!
Hi Denisse;
you are talking about Step 10: Selecting Installation features ?
And you only see the managements tools..
hum...
Quickly thinking I see only two reasons:
1- You haven't use a correct SQL 2008 installation package
2- You are trying to install SQL server on a server that is not planned to be a Database Server.
When you install Windows 2008 on a machine you have to choose what is the server for, you have many options. I think for example that if you choose the "Web Server" option, you won't be allowed to install a Server product on the machine (I had this problem with SharePoint)
I think that in your case the second cause is the more probable...
Hope you find the solution!
Tell us what it was :-)
Marc
Post a Comment