A Step by Step guide to installing SQL Server 2008

AAAA StepStepStepStep bybybyby StepStepStepStep guideguideguideguide totototo installinginstallinginstallinginstalling SQLSQLSQLSQL ServerServerServerServer 2008200820082008 simplysimplysimplysimply andandandand successfullysuccessfullysuccessfullysuccessfully withwithwithwith nononono priorpriorpriorprior knowledgeknowledgeknowledgeknowledgeDevelopers and system administrators will find this installation guide useful, as will seasoned DBAs. It will teach you the basics required for a typical, problem-free installation of SQL Server 2008, allowing you to add other components later if you wish. RememberRememberRememberRemember totototo installinstallinstallinstall thethethethe .Net.Net.Net.Net FrameworkFrameworkFrameworkFramework 3.53.53.53.5Before you start the installation, you’ll need to install the .Net 3.5 Framework. This comes pre-installed on Windows 2008 Server, but for earlier versions of Windows, you’ll need to install it first. This is a straightforward pre-requisite and is usually included as part of the SQL Server 2008 installation. However, if you don’t know how to do this, or for some reason you need to download it, check out the guide Installing .Net Framework 3.5 for SQL Server 2008. Once this Framework in installed you can commence the installation of SQL Server 2008. STEPSTEPSTEPSTEP 1111 :::: CopyCopyCopyCopy thethethethe installationinstallationinstallationinstallation filesfilesfilesfilesFirst off I’d recommend you copy the entire directory structure from the SQL Server 2008 installation disc to the C: drive of the machine you are going to install it on. Although this means you need to grab a cup of coffee whilst it’s copying, this has three advantages: • It makes the installation process much faster than running it from CD/DVD once it gets started. • It allows you to easily add or remove components later, without having to hunt around for the CD/DVD. • If your media is damaged and a file won’t copy, you get to find out now, rather than halfway through the installation. Here’s what my system looks like after the copy: STEPSTEPSTEPSTEP 2222 :::: Setup.exeSetup.exeSetup.exeSetup.exeDouble click on the setup.exe file. After a few seconds a dialog box appears: This will disappear from the screen and then the main installation page appears: STEPSTEPSTEPSTEP 3333 :::: SQLSQLSQLSQL ServerServerServerServer InstallationInstallationInstallationInstallation CenterCenterCenterCenter Click on the Installation hyperlink on the left hand side of the screen: STEPSTEPSTEPSTEP 4444 :::: SQLSQLSQLSQL ServerServerServerServer InstallationInstallationInstallationInstallation CenterCenterCenterCenterClick on the "New"New"New"New ServerServerServerServer stand-alonestand-alonestand-alonestand-alone installation"installation"installation"installation" link on the right side of the screen: The following dialog appears on the screen whilst the install program prepares for installation: After a minute or so (the timing will vary according to your system), the following screen appears: STEPSTEPSTEPSTEP 5555 (optional)(optional)(optional)(optional) :::: If any checks have failed, click on the Show details button or "View detailed report link" to find out the cause, correct it, then click on the Re-run button to perform the checks again. STEPSTEPSTEPSTEP 6666 :::: ProductProductProductProduct keykeykeykey If all checks have passed, click on the OK button. After a few moments, the option to select the edition and to enter the license key (or “product key”) will appear. Note that the product key box may already be populated, depending on which edition you have. Don’t enter the product key we’ve shown here, it won’t work on your system!: STEPSTEPSTEPSTEP 7777 :::: LicenseLicenseLicenseLicense TermsTermsTermsTermsEnter the product key into the box, or choose the free edition if you're evaluating SQL Server 2008, and click on the Next button: Click in the "I"I"I"I acceptacceptacceptaccept thethethethe licenselicenselicenselicense terms"terms"terms"terms" check box, then click on the NextNextNextNext button again. STEPSTEPSTEPSTEP 8888 :::: SetupSetupSetupSetup SupportSupportSupportSupport FilesFilesFilesFiles The following screen appears; click on the Install button: The following screen will appear whilst Windows Installer prepares itself for the installation. This will take a short while: After 30 seconds or so the dialog appears again: STEPSTEPSTEPSTEP 9999 :::: SetupSetupSetupSetup SupportSupportSupportSupport RulesRulesRulesRules If all is well, the following screen appears: Click on the NextNextNextNext button again. STEPSTEPSTEPSTEP 10101010 :::: FeatureFeatureFeatureFeature SelectionSelectionSelectionSelection SelectSelectSelectSelect thethethethe featuresfeaturesfeaturesfeatures youyouyouyou wantwantwantwant totototo install.install.install.install. At a minimum, the following are useful (I'd argue essential), but what you need will depend on your needs: Click on the NextNextNextNext button. STEPSTEPSTEPSTEP 11111111 :::: InstanceInstanceInstanceInstance ConfigurationConfigurationConfigurationConfiguration After a short while the following screen appears: For most installations, keep the default settings. Click on the NextNextNextNext button. STEPSTEPSTEPSTEP 12121212 :::: DiskDiskDiskDisk SpaceSpaceSpaceSpace RequirementsRequirementsRequirementsRequirements This screen just tells you if you have sufficient disk space on the drive you’re installing to, and what’s going to be installed where. Click on NextNextNextNext. STEPSTEPSTEPSTEP 13131313 :::: ServerServerServerServer ConfigurationConfigurationConfigurationConfiguration This step allows you to set up the service accounts that will be used to run SQL Server. If you have created Windows NT or Active Directory accounts for use with services, use these. If not, then just to get the installation up and working, use the built-in Network Service account for all three services listed (this account does not require a password). This allows SQL Server to start up after installation. However, it can be easily changed later to another account through the Services applet (Control Panel -> Administrator Tools -> Services): In addition, remember to change the StartupStartupStartupStartup TypeTypeTypeType to AutomaticAutomaticAutomaticAutomatic, for all three services. This automatically starts the SQL Server database engine, SQL Agent and SQL Browser services when the server is re-booted. The first service runs the SQL Server database engines executable process. The other two services allow scheduled jobs to run after installation (and after a re-boot), and allow the SQL Server to be found by clients on the network. Do not worry about changing the collation tab, unless there is a specific requirement for anything other than the default collation sequence. Finally, click on NextNextNextNext. STEPSTEPSTEPSTEP 14141414 :::: DatabaseDatabaseDatabaseDatabase EngineEngineEngineEngine ConfigurationConfigurationConfigurationConfiguration –––– AccountAccountAccountAccount ProvisionProvisionProvisionProvision This screen allows you to set up database engine security. Change the AuthenticationAuthenticationAuthenticationAuthentication ModeModeModeMode to MixedMixedMixedMixed ModeModeModeMode unless you are certaincertaincertaincertain you only need Windows-only authentication. • ManyManyManyMany thirdthirdthirdthird partypartypartyparty applicationsapplicationsapplicationsapplications relyrelyrelyrely onononon SQLSQLSQLSQL ServerServerServerServer loginsloginsloginslogins totototo operateoperateoperateoperate correctly,correctly,correctly,correctly, sosososo ifififif youyouyouyou areareareare settingsettingsettingsetting upupupup aaaa serverserverserverserver forforforfor aaaa thirdthirdthirdthird partypartypartyparty application,application,application,application, ratherratherratherrather thanthanthanthan oneoneoneone developeddevelopeddevelopeddeveloped in-house,in-house,in-house,in-house, enablingenablingenablingenabling MixedMixedMixedMixed ModeModeModeMode authenticationauthenticationauthenticationauthentication isisisis aaaa goodgoodgoodgood idea.idea.idea.idea. If you pick Mixed Mode security, you must also enter a password for the sysadmin account (sa). Enter and confirm a secure password for the sa account and keep it somewhere safe. Do not give it to any one you do not want to have access to the SQL Server. Note that you MUST also provide a Windows NT account on the local machine as a SQL Server administrator. If you do not want Windows system administrators to be able walk up to the box and login to SQL Server, create a new, local, dummy Windows user and add this account instead. Otherwise, add in the local administrator account, or your own Windows account on the domain in which the SQL Server will reside. STEPSTEPSTEPSTEP 15151515 :::: DatabaseDatabaseDatabaseDatabase EngineEngineEngineEngine ConfigurationConfigurationConfigurationConfiguration –––– DataDataDataData DirectoriesDirectoriesDirectoriesDirectories Click on the DataDataDataData DirectoriesDirectoriesDirectoriesDirectories tab. Change the directories to specify which drives in your system will be used for the various types of database files. Generally it’s advisable to put the User database directory and User log directory on separate physical drives for performance, but it will depend on how Windows has been configured and how many disk drives you have available. If you are installing on a single drive laptop or desktop, then simply specify: DataDataDataData rootrootrootroot directorydirectorydirectorydirectory C:\Program Files\Microsoft SQL Server UserUserUserUser databasedatabasedatabasedatabase directorydirectorydirectorydirectory C:\Data UserUserUserUser loglogloglog directorydirectorydirectorydirectory C:\Logs TempTempTempTemp DBDBDBDB directorydirectorydirectorydirectory C:\TempDB TempTempTempTemp LogLogLogLog directorydirectorydirectorydirectory C:\TempDB BackupBackupBackupBackup directorydirectorydirectorydirectory C:\Backups Do not click on the FILESTREAMFILESTREAMFILESTREAMFILESTREAM tab unless you know you need to change these options, as it is not generally required for most installations, but can easily be changed by using sp_configure 'filestream_access_level', ''after SQL Server has been installed. Click on NextNextNextNext. STEPSTEPSTEPSTEP 16161616 :::: ErrorErrorErrorError UsageUsageUsageUsage ReportingReportingReportingReportingThis screen simply asks if you want to send error information to Microsoft and can safely be skipped if you do not want to share any information. Click boxes if you want to help Microsoft help you. Click on NextNextNextNext again… STEPSTEPSTEPSTEP 16161616 :::: InstallationInstallationInstallationInstallation RulesRulesRulesRules This screen simply checks if there are any processes or other installations running which will stop the installation of SQL Server 2008. Click on NextNextNextNext again – you’re almost ready to install: STEPSTEPSTEPSTEP 17171717 :::: ReadyReadyReadyReady totototo InstallInstallInstallInstallThis screen summarises what you are about to install and gives you a last chance to cancel or change anything that’s wrongly configured: Check that what’s being installed is what you want and then click on InstallInstallInstallInstall when you’re sure you want to start the installation process: InstallationInstallationInstallationInstallation ProgressProgressProgressProgressSQL Server 2008 will now install. How long it takes depends on the speed of your machine, what load it’s under, the installation media (CD is slower) and what you’ve chosen to install. …………MoreMoreMoreMore InstallationInstallationInstallationInstallation ProgressProgressProgressProgress ............ andandandand FinallyFinallyFinallyFinally Finally, the installation will complete: ...and the following dialog box will appear: ClickClickClickClick onononon OK,OK,OK,OK, thethethethe machinemachinemachinemachine willwillwillwill NOTNOTNOTNOT reboot.reboot.reboot.reboot. The following will appear: …followed by: ClickClickClickClick onononon thethethethe NextNextNextNext buttonbuttonbuttonbutton again...STEPagain...STEPagain...STEPagain...STEP 18181818 :::: InstallationInstallationInstallationInstallation CompleteCompleteCompleteComplete The following screen appears: It may be worth clicking on the installation log at the top of the screen to check everything’s gone as expected. Not that this is MUCH smaller than the usual SQL Server installation log files of old. Finally, clickclickclickclick onononon thethethethe CloseCloseCloseClose buttonbuttonbuttonbutton. The following dialog will appear: ClickClickClickClick onononon OKOKOKOK –––– youryouryouryour serverserverserverserver willwillwillwill NOTNOTNOTNOT re-bootre-bootre-bootre-boot atatatat thisthisthisthis point.point.point.point. The dialog box will disappear and you will be returned to the Installation Center: ClickClickClickClick onononon thethethethe CloseCloseCloseClose buttonbuttonbuttonbutton (the “x”) in the top right of the screen. Finally, manually reboot your machine to complete the SQL Server 2008 installation. TopTopTopTop TipsTipsTipsTips :::: HowHowHowHow totototo checkcheckcheckcheck thatthatthatthat SQLSQLSQLSQL ServerServerServerServer 2008200820082008 hashashashas installedinstalledinstalledinstalled correctlycorrectlycorrectlycorrectlyHere are a short number of post-installation checks which are useful to perform after re-booting your new SQL Server. You don’t have to run these, and there are other ways to check, but they are very useful for non-DBAs to be sure that the installation is basically sound and a connection can be made to the new SQL Server before handing it over to someone else. CheckCheckCheckCheck 1:1:1:1: HasHasHasHas thethethethe SQLSQLSQLSQL ServerServerServerServer ServiceServiceServiceService Started?Started?Started?Started?Check SQL Server 2008 has started. CheckCheckCheckCheck 2:2:2:2: DoesDoesDoesDoes ManagementManagementManagementManagement StudioStudioStudioStudio Work?Work?Work?Work? Check Management Studio works by firing it up. ClickClickClickClick onononon NONONONO when you see this dialog box: CheckCheckCheckCheck 3:3:3:3: CanCanCanCan youyouyouyou runrunrunrun aaaa basicbasicbasicbasic queryqueryqueryquery againstagainstagainstagainst thethethethe newnewnewnew SQLSQLSQLSQL Server?Server?Server?Server?Check SQL Server works by running a simple query from Management Studio: Enter the query shown below and hit F5 to run it: CheCheCheChe ckckckck 4:4:4:4: IsIsIsIs SQLSQLSQLSQL ServerServerServerServer AgentAgentAgentAgent Running?Running?Running?Running? Check SQL Server Agent is running for scheduled jobs. There should be a green arrow next to the SQL Server Agent database symbol (it’s small, you might have to look hard): CheckCheckCheckCheck 5:5:5:5: CanCanCanCan SQLSQLSQLSQL ServerServerServerServer bebebebe seenseenseenseen fromfromfromfrom thethethethe Network?Network?Network?Network?Check that the new SQL Server can be seen from another SQL Server on the same domain by running isql –L (or osql –L): If you can’t see the new SQL Server in this list, check that the SQL Server Browser service is started on the machine where you have just installed SQL Server. CheckCheckCheckCheck 6:6:6:6: HasHasHasHas thethethethe TCP/IPTCP/IPTCP/IPTCP/IP networknetworknetworknetwork protocolprotocolprotocolprotocol librarylibrarylibrarylibrary beenbeenbeenbeen enabledenabledenabledenabled onononon thethethethe server?server?server?server? If the browser service is started but you still cannot connect to the server, click on StartStartStartStart ->Programs->Programs->Programs->Programs ->->->-> SQLSQLSQLSQL ServerServerServerServer 2008200820082008 ->->->-> SQLSQLSQLSQL ServerServerServerServer ConfigurationConfigurationConfigurationConfiguration ManagerManagerManagerManager (on the server where SQL Server’s just been installed) The SQL Server Configuration Manager window opens. Click on the SQLSQLSQLSQL ServerServerServerServer NetworkNetworkNetworkNetwork ConfigurationConfigurationConfigurationConfiguration node and expand it. In the example below, we have MSSQLSERVER (a base instance of SQL Server), and SQLEXPRESS showing as installed. If in doubt, click on ProtocolsProtocolsProtocolsProtocols forforforfor MSSQLSERVERMSSQLSERVERMSSQLSERVERMSSQLSERVER. In the above screenshot, the TCP/IP network protocol library is disabled. We need to enable it in order that remote servers can talk to the newly installed SQL Server. • AAAAwordwordwordword ofofofof explanationexplanationexplanationexplanation :::: In most installations, Named Pipes can be ignored, unless there is a requirement for it. In virtually all environments, VIA can also be ignored as this protocol requires a special network card. Shared memory is the “local” protocol that SQL Server uses when talking to a client application on the same server as itself, for example when SQL Server Management Studio connects to it. It is usually best to leave this enabled. You will need the TCP/IP protocol enabled if you need to connect to your new SQL Server from a remote client or another server via TCP/IP, which is what most networks use. If it shows as DISABLEDDISABLEDDISABLEDDISABLED (above), doubledoubledoubledouble clickclickclickclick onononon thethethethe TCP/IPTCP/IPTCP/IPTCP/IP protocolprotocolprotocolprotocol linelinelineline, and the following window will appear: EnsureEnsureEnsureEnsure that EnabledEnabledEnabledEnabled isisisis setsetsetset totototo YesYesYesYes, and click on OK. The following warning will appear: Click on OK, and you will be returned to the Configuration Manager window, where TCP/IP will now be shown as enabled: Go back to the Services applet, and re-start the MSSQLSERVER service so that the TCP/IP protocol can be used to connect to your new SQL Server. Then try to connect to it again from a remote machine. If you have experienced problems with the previous connectivity tests, you should now be able to repeat at least some of them successfully.