Unless you have an MSDN subscription (Universal, Enterprise, or Professional) the only thing to work with is the SQL Server 2005 Beta 2 Express Edition, available at www.microsoft.com/
downloads/details.aspx?FamilyID=62B348BB-0458-4203-BB03-8BE49E16E6CD&
displaylang=en.
The SQL Server Express Edition is the next version of MSDE. The Beta 2 version is an evaluation version and is good up to 18 months from the date of installation. After the evaluation period is over, no SQL Server services will start.
Like its bigger brothers (SQL Server 2005 Enterprise Edition and SQL Server 2005 Developer Edition), the Express Edition also needs the .NET Framework 2.0. But unlike its bigger brothers, the Express Edition does not install it. You have to do that yourself — at least in Beta 2.
You can get the .NET Framework 2.0 from www.microsoft.com/downloads/details.aspx?
familyid=B7ADC595-717C-4EF7-817B-BDEFD6947019&displaylang=en.
Installing SQL Ser ver 2005
Begin the installation by running the Setup.exein the root of the CD/DVD or if Autorun does not automatically begin the installation.
The first screen to appear is the Welcome/Start screen. Here you have several options. This is a good place to review the requirements for running SQL Server 2005 by selecting the Review hardware and software requirements link.
To begin the actual installation, click the Run the SQL Server Installation Wizard link shown in Figure 3-1.
Figure 3-1
The first part of the installation installs software that is necessary prior to installing SQL Server 2005.
Three components are required before the installation of SQL Server 2005 can begin: the .NET
Framework 2.0, Microsoft SQL Native Client, and Microsoft SQL Server 2005 Beta 2 Setup Support Files, as shown in Figure 3-2.
Figure 3-2
The first prerequisite component is the .NET Framework 2.0. As discussed in Chapter 1, SQL Server 2005 uses version 2.0 of the .NET Framework. Luckily, SQL Server 2005 installs version 2.0 for you.
Once all the perquisite components have been installed, click Finish. At this point the SQL Server instal-lation begins, as shown in Figure 3-3.
Click Next to begin the installation of SQL Server 2005.
Figure 3-4 shows an important step in the installation process: the System Configuration Check, or SCC.
It verifies a total of twelve items of your system to make sure that your system on which to install SQL Server is configured correctly.
Figure 3-4
We’re lucky this process does not take long and it actually makes multiple checks at one time. The SCC is quite thorough and does not allow the installation to continue if certain requirements are not met. For example, it generates a warning if the computer that SQL Server 2005 is being installed on is less than 600 MHz, but it will not stop the installation.
As another example, if the system on which SQL Server 2005 is being installed on has less than 128MB of RAM, it does not allow the installation to continue. It also generates a warning if the amount of memory is between 128MB and 256MB of RAM.
For a complete list of SCC checks, see the online help under the topic system configuration checker.
The Continue button is available only if all check results are successful, or if failed checks are non-fatal.
For any failed check items, resolution to blocking issues is included with results in the report.
If everything passes and you are given the green light, click Continue.
The next screen, shown in Figure 3-5, allows you to choose which components you want to install.
Obviously you want to choose the first option, SQL Server, as that is the minimum required component to run SQL Server 2005. You may also want to select the Workstation components, Books Online and development tools option, which installs some of the components and tools with which to administer SQL Server 2005. Selecting one of these components selects the minimum features necessary to run SQL Server 2005. It is similar to selecting a Typical installation.
Figure 3-5
One of the new features in the installation is the capability to install SQL Server 2005 as a virtual server.
Virtual server enables you to run multiple instances of an OS on a single computer. Think of it as run-ning multiple computers on a single computer. You can select the Install as virtual server option if you want SQL Server to support it.
Also included in the installation is Reporting Services, which was a separate installation for SQL Server 2000.
For a more detailed installation, click the Advanced button, which displays a detailed list of items, shown in Figure 3-6. This option allows you to select which features you want based on the components you selected in the previous step, as well as allowing you to select more detailed features as opposed to a generic component on the previous screen. For example, selecting the SQL Server component on the previous screen basically tells the installer that you want to install SQL Server 2005. This screen lets you select detailed installation options for the SQL Server component such as Replication and Full-Text Search.
If you overlooked a component you wanted to install on the previous installation step, you can either select it here or click the Back button to select the desired component. Selecting the components on the Feature Selection screen is preferable over going back because you can select the features for that compo-nent and not have to go back.
Figure 3-6
Any feature preceded by a red X means that component will not be installed. Any feature preceded by a white box means that feature will be installed. Any feature preceded by a gray box typically means that you can expand that node and select subfeatures. Most likely, some of those subfeatures have not been selected for installation. You should expand that tree node and preview those subfeatures, as there might be some that you want to install.
If you have already installed SQL Server 2005 and are running the installation again, this screen is used to add and remove features.
Click the Next button once you are satisfied with your feature selection.
The next screen in the installation process, shown in Figure 3-7, allows you to select the instance in which you would like to install SQL Server 2005. Just like SQL Server 2000, you can run multiple instances of SQL Server 2005 on a computer.
Be sure that you install the sample databases, primarily the AdventureWorks database, because you will be working with them throughout the book. They can be installed by expanding the Documentation and Samples node and selecting the Databases node.
Figure 3-7
The Default instance is the default selection. If you install SQL Server 2005 a second time and select the Default instance, the installation will ask you if you want to upgrade your existing Default instance. The same goes for a Named instance. If you type in a Named instance that already exists, the installer will ask you if you would like to upgrade that instance.
Each instance of SQL Server runs in its own specific space. In other words, it has its own set of services with its own settings, such as collation and other options.
Except for the first installation, you should select a Named instance for each subsequent installation and give that installation a unique instance name, unless you plan on upgrading the desired instance to add or remove features.
Once you have selected the instance in which to install SQL Server, click Next.
The next step in the installation process is the Service Account setup. This screen (see Figure 3-8) lets you define which services run under which account. You can customize each service to start under a specific account or you can use the built-in System account. This screen also lets you determine which services are automatically started when the SQL Server 2005 computer is started.
Once you have configured the services, click Next.
The next step in the installation process is the selection of the Authentication Mode, as shown in Figure 3-9. This step defines the credentials with which you will be connecting (authenticating) to SQL Server 2005.
Figure 3-8
Figure 3-9
Just as in the previous version of SQL Server, SQL Server 2005 gives you two options for authentication:
Windows Authentication Mode or Mixed Mode authentication.
Windows Authentication connects the user to SQL Server through a Windows user account. SQL Server validates the account credentials (user name and password) via the Windows operating system.
Mixed Mode authentication allows the user to connect either via Windows authentication or SQL Server authentication.
If you select Mixed Mode authentication, be aware that there are some changes in SQL Server 2005. New for this release is Strong Password enforcement. No longer will SQL Server allow you to get away with blank passwords or using “password” as the password.
For example, if you type in “password” for the sa password, you receive the message shown in Figure 3-10.
Figure 3-10
In fact, SQL Server 2005 does not allow the following as passwords for the sa account:
❑ Blank passwords
❑ The word “Password” or “password”
❑ The word “Admin” or “admin”
❑ The word “Administrator” or “administrator”
❑ The word “sysadmin” or “Sysadmin”
❑ The acronym “sa”
All passwords used must meet a certain set of requirements before SQL Server lets you use them. Any password must meet three of the following four requirements:
❑ Must contain uppercase letters
❑ Must contain lowercase letters
❑ Must contain numbers
❑ Must contain non-alphanumeric characters, such as #, $, &, or @
As the error message suggests, see Authentication Mode in the Books Online for more information on strong passwords. The read is well worth your time.
Once you have set your authentication mode, click Next.
The final step in the installation process is setting the collation. Figure 3-11 shows the options available for setting collation and sort order for SQL Server 2005. Collation specifies the SQL Server sorting behav-ior, meaning how character strings are sorted and compared.
If you don’t have any specific sorting or case-sensitivity needs, the default sort order works for most installations.
Figure 3-11
Use the top part of this screen when the installation of SQL Server must match the collation settings of another instance of SQL Server or if it must match the Windows local settings of another computer run-ning SQL Server.
Use the SQL collation section for backward compatibility with earlier versions of SQL Server. You should select this option if you want to match compatible settings with SQL Server 8.0 (SQL Server 2000), 7.0, or earlier.
SQL collation cannot be used with Analysis Services. If you select to install SQL Server Analysis Services, SQL Server tries to match the best Windows collation for Analysis Services, based on the SQL collation you select. If the SQL Server collation and Analysis Services collation do not match, your results may not be consistent.
Your best bet is to use Windows collation for both.
To select separate collation settings for SQL Server and Analysis Services, select the Customize for each service account check box. This enables the drop-down list of services from which to select the desired service. Select the service, and then select your collation and sort order.
After you select the appropriate sort order, click Next.
The next screen in the installation is the Report Server setup. If you did not select to install the Reporting Services on the Feature Selection screen, you will not see the screen. If you did select Reporting Services, this step allows you specify how a Report Service instance is installed.
You can install the default configuration, which installs and configures Report Server for you, or you can install the Report Server, and after the installation is complete you can configure Reporting Services via the Reporting Services Configuration Tool.
If you select the option to install the default configuration, clicking the Details button displays a screen with information for the default configuration (see Figure 3-12).
Figure 3-12
After you configure this screen, click Next.
The next screen in the wizard is the Error and Usage Report Settings (see Figure 3-13), which allows you to automatically send feedback to Microsoft for any errors generated or features used.
Microsoft uses these error reports to improve SQL Server functionality. All information is treated as confidential.
Figure 3-13
If you select to send Feature Usage data (the second checkbox in Figure 3-13), SQL Server is configured to occasionally send a report to Microsoft containing information about how you are using SQL Server 2005. This information is also treaded confidentially.
After you make your selections on this screen, click Next.
The next screen in the setup wizard is the overview of the options you selected during the configuration of the setup (see Figure 3-14). You can look over the items you selected, and by clicking the Back button you can change any items.
Figure 3-14
If you are satisfied with the selections you made, click Install. At this point the installation begins and you should see a screen that displays the installation progress, similar to Figure 3-15.
At the end of the installation, you may be required to reboot. At this point, SQL Server 2005 is installed and you are almost ready to go. Why almost? You need to set a couple of configuration items before you use some of the examples in this book. As well, if you are using SQL Server 2005 and Visual Studio on separate machines, you need to tell SQL Server about it.
By default, SQL Server 2005 does not accept remote connections. So if you plan to run SQL Server 2005 and Visual Studio 2005 on separate computers, you need to tell SQL Server that connections will be com-ing in from a remote computer.
You can find this configuration, along with most other SQL Server 2005 configuration items, by opening the Surface Area Configuration form, shown in Figure 3-16.
Figure 3-15
Figure 3-16
First, to tell SQL Server to accept remote connections, select the top option, Surface Area Configuration for Services and Connections. This opens the corresponding form, shown in Figure 3-17.
Figure 3-17
To enable remote connections, select the Remote Connections option on the left side of the form. You will notice that by default, SQL Server accepts only local connections. To enable remote connections, click the Local and Remote Connections radio button. This will allow you to select three connection options.
Typically, using TCP/IP only will suffice, but if your environment requires a different selection, make the selection and click OK.
The next step is to enable the CLR, which is turned off by default. Back on the main screen (shown previ-ously in Figure 3-16), select the bottom option, Surface Area Configuration for Features to open the form displayed in Figure 3-18.
To enable the CLR, select the CLR Integration option on the left and then click the Enable CLR Integration check box on the right. Click OK to save the changes.
Now you are ready to go!
Figure 3-18
Summar y
This chapter walked you through basic steps of installing SQL Server 2005 and highlighted some areas of detail, as well as pointed out some differences between SQL Server 2005 and previous versions of SQL Server. With SQL Server installed, you can now easily work with the examples throughout the book.
By now you should have good grasp of what’s new in SQL Server 2005 and an idea of what’s coming up in later chapters. The next few chapters deal with topics that, while not directly specific to SQL Server, will be of great benefit to you in the last half of this book. In particular, the next chapter covers the new xmldata type.