Figure 3.4 SQL Server Configuration Manager 92 Chapter3•ConfiguringSQLServer2008 Managing Services Launching Configuration Manager connects you to the local server and displays all of the SQL Server Services installed locally. Figure 3.4 shows Configuration Manager after completing Exercise 3.1. You can see the two instances that are installed as well as the Analysis Services and Reporting Services installations, and can start, stop, and restart the services by right-clicking on the appropriate instance. Note that the two SQL Server Agent Services are stopped and set to start manually. Right-clicking on a service and selecting Properties gives you access to four tabs, the first of which allows you to change the account that the service logs on with. In Figure 3.5 you can see that SQL1 is currently running using the Network Service account, and you can change it here to run using a dedicated Windows account. It’s a Microsoft best practice for SQL Server to run using a dedicated Windows account. Figure 3.5 Changing the Service Account ConfiguringSQLServer2008•Chapter3 93 If you need to change the service account for any of the SQL Server services, then this is the only supported method to do it. SQL Server Configuration Manager assigns additional advanced user rights to the accounts when the service is config- ured, which won’t get assigned if you just use the Services applet in control panel. The Service tab allows you change the startup type of the service to Automatic, Manual, or Disabled. They work the same way as any other Windows service, but it’s worth noting that if you are running SQL Server 2008 on a Windows failover cluster you will see all the services set to start manually. This is because the failover cluster software manages when the services get started and stopped; they don’t get started in the normal way by Windows during startup. They will be stopped on passive nodes and started on active nodes. The Advanced tab provides access to change whether or not you want to automatically provide feedback or errors to Microsoft; where SQL Server should store memory dumps in the event of failure; and most importantly, the startup parameters to use when starting the SQL Server Service. In Figure 3.6 you can see an expanded view of the default startup parameters as well as a trace flag that has been set to run on startup. Trace flags enable different behaviors in SQL Server, and different flags can be enabled on startup by using the –T switch. In this example trace flag 1222 has been enabled on startup, which will dump detailed data to the error log in the event that a deadlock has been encountered on the server. Figure 3.6 Viewing and Changing Startup Parameters 94 Chapter3•ConfiguringSQLServer2008 Enabling FileStream FileStream is a new feature in SQL Server 2008 that allows applications to store unstructured data, such as documents and images, in the file system rather than directly in SQL Server. This allows applications to take advantage of the optimizations that Windows has for dealing with files rather than forcing it all to be stored directly in the database. Using FileStream is outside the scope of this exam but you will need to know how to enable it. Enabling FileStream is done in two parts: one for Windows and one for SQL Server. However, if you enable FileStream during the SQL Server installation process, then both parts are done for you. To enable FileStream after installation you first need to enable it for Windows, and this is done through SQL Server Configuration Manager. If you look at the properties of the SQL Server Service you’ll see a new tab for SQL Server 2008 called FILESTREAM. On the new tab, the first option you have is to Enable FILESTREAM for Transact-SQL access and is mandatory for any level of FileStream access. This allows you to work with FileStream data using Transact-SQL statements. The second option enables the use of file I/O streaming access. What this means is FileStream access through other programming languages using the Win32 APIs. This option requires a fileshare to be created to access the files and has an additional Figure 3.7 Enabling FILESTREAM in SQL Server Configuration Manager Value Description 0 Disables FILESTREAM support for this instance 1 Enables FILESTREAM for Transact-SQL access 2 Enables FILESTREAM for Transact-SQL and Win32 streaming access Table 3.2 Values for sp_configure filestream_access_level ConfiguringSQLServer2008•Chapter3 95 option of whether to allow remote clients to access the FileStream data. In Figure 3.7 you can see that FILESTREAM access has been enabled on SQL1 for Transact-SQL access and file I/O streaming using a fileshare called SQL1. Once the SQL Server Service is configured to allow FileStream access, you need to enable it within SQL Server itself using the filestream_access_level option. This is modified using the sp_configure command, valid values for which can be found in Table 3.2. sp_configure is covered in more depth later in this chapter. If you enabled FILESTREAM during the SQL Server installation process, this option will have been configured for you. You will only need to modify it to make a change post installation. Edition Shared Memory TCP/IP Named Pipes VIA Enterprise Enabled Enabled Local:Enabled, Disabled Remote:Disabled Standard Enabled Enabled Local:Enabled, Disabled Remote:Disabled Workgroup Enabled Enabled Local:Enabled, Disabled Remote:Disabled Developer Enabled Disabled Local:Enabled, Disabled Remote:Disabled Evaluation Enabled Disabled Local:Enabled, Disabled Remote:Disabled Express Enabled Disabled Local:Enabled, Disabled Remote:Disabled Table 3.3 Default SQL Server Network Configuration 96 Chapter3•ConfiguringSQLServer2008 Managing Connections and Protocols The network protocols used to communicate with SQL Server are managed using SQL Server Configuration Manager but depend on the protocols being configured already at the operating system level. SQL Server 2008 can communicate using four different protocols. Table 3.3 provides the default state for each protocol by edition of SQL Server. Shared Memory Simple and fast, Shared Memory is the default protocol used to connect from a client running on the same computer as SQL Server. It has no configurable properties and is always tried first when connecting, but it can be disabled to help troubleshoot connectivity issues with other protocols. For example, you have remote applications that can’t connect to SQL Server via TCP/IP, so you logon to the server, ensure that TCP/IP is configured properly, disable Shared Memory, and connect using SQL Server Management Studio. If you can connect locally using TCP/IP you know that SQL Server is configured correctly, which helps to rule out a SQL Server configuration issue as the cause of the problem. . 3.4 SQL Server Configuration Manager 92 Chapter3•Configuring SQL Server 2008 Managing Services Launching Configuration Manager connects you to the local server and displays all of the SQL Server. look at the properties of the SQL Server Service you’ll see a new tab for SQL Server 2008 called FILESTREAM. On the new tab, the first option you have is to Enable FILESTREAM for Transact -SQL. for any of the SQL Server services, then this is the only supported method to do it. SQL Server Configuration Manager assigns additional advanced user rights to the accounts when the service