Spotlight on SQL Server 8.1. Deployment Guide

Transcription

1 Spotlight on SQL Server 8.1 Deployment Guide

2 2011 Quest Software, Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser s personal use without the written permission of Quest Software, Inc. The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON- INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document. If you have any questions regarding your potential use of this material, contact: Quest Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA [email protected] Refer to our Web site ( for regional and international office information. Patents Protected by U.S. Patent #6,901,582. Additional patents pending. Trademarks Quest, Quest Software, the Quest Software logo and Spotlight are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. For a complete list of Quest Software s trademarks, please see Other trademarks and registered trademarks are property of their respective owners. Spotlight on SQL Server 8.1 Deployment Guide Monday, 26 September 2011

3 Table of Contents Deployment Checklist 6 Deployment Guidelines 7 About Spotlight on SQL Server 7 Enterprise Edition vs Desktop Edition 7 Spotlight on SQL Server Architecture 8 Deployment Scenarios 8 Scenario 1: Monitor 1 25 SQL Server instances 8 Scenario 2: Monitor SQL Server instances 9 Co-existence with Performance Analysis 10 Spotlight on SQL Server and Windows domains 10 Spotlight on SQL Server and Firewalls 10 If the firewall is on the same machine as the diagnostic server 10 If the diagnostic server and monitored SQL Servers are inside the DMZ 11 If the diagnostic server is outside the DMZ; the monitored SQL Servers are inside the DMZ 11 Size Requirements 13 Diagnostic Server 13 Spotlight Client 13 Spotlight Statistics Repository 13 Playback Database 13 Permissions and Requirements 15 Diagnostic Server Machine 15 Permissions 15 Requirements 17 Spotlight Client Machine 22 Permissions 22

4 Table of Contents 4 Requirements 24 SQL Server Machine 25 Permissions 25 Requirements 26 Spotlight Statistics Repository 28 Requirements 29 Playback Database 30 Requirements 30 Maintenance Plan for Spotlight Statistics Repository and Playback Database 31 Database Configuration 31 Fragmentation and Index Performance 31 Database Backup 32 Installation and Upgrade 33 Enterprise Edition 33 Install Enterprise Edition 33 Upgrade Enterprise Edition 34 Uninstall Enterprise Edition 35 Desktop Edition 36 Install Desktop Edition 36 Upgrade Desktop Edition 37 Uninstall Desktop Edition 38 Configure 39 Configure the Playback Database 40 Configure the Spotlight Statistics Repository 41 Change the Diagnostic Server Address 42 Back Up Spotlight Configuration Data 43

5 Table of Contents 5 Appendix: Contact Quest 44 Contact Quest Support 44 Spotlight Support 44 Contact Quest Software 45 About Quest Software 45 Appendix: Third Party Contributions 46 Index 48

6 1 Deployment Checklist Complete this checklist before installing and configuring Spotlight on SQL Server. Review deployment guidelines See Deployment Guidelines (page 7). Check connectivity See Spotlight on SQL Server and Windows domains (page 10) and Spotlight on SQL Server and Firewalls (page 10). Check disk space requirements See Size Requirements (page 13). Check Diagnostic Server permissions and requirements See Diagnostic Server Machine (page 15). Check Spotlight client permissions and requirements See Spotlight Client Machine (page 22). Check monitored SQL Server permissions and requirements See SQL Server Machine (page 25). Review historical repository requirements See Spotlight Statistics Repository (page 28) and Playback Database (page 30).

7 2 Deployment Guidelines About Spotlight on SQL Server Spotlight on SQL Server monitors the activity of SQL Server instances. At the core of its architecture is a Diagnostic server that supplies data to Spotlight Client(s) in real time. Recent history is stored in the Playback Database. Long term history for reporting and trending is stored in the Spotlight Statistics Repository. Enterprise Edition vs Desktop Edition There are two editions of Spotlight on SQL Server. The Enterprise Edition is fully configurable. The Desktop Edition is limited as per the following specifications. Features Enterprise Edition Desktop Edition Spotlight Clients At least 1 1 Diagnostic Server At least 1 1 Playback Database 7 days of playback data by default; configurable. 4 hours of playback data; non configurable. Heat Map Yes No Spotlight Statistics Repository and Spotlight Reporting and Trending Yes No notifications on alarms Yes No Upload data to Project Lucy Yes Yes Monitored Connections Microsoft SQL Server Yes Yes Microsoft SQL Server Replication Yes No Microsoft Windows Yes Yes Microsoft SQL Server Analysis Services Yes Yes Microsoft SQL Azure Database Yes Yes

8 Deployment Guidelines 8 Features Enterprise Edition Desktop Edition VMware Server Yes No Spotlight on SQL Server Architecture The diagram represents a classic Spotlight on SQL Server Enterprise Edition architecture. The Diagnostic Server connects to the SQL Server instances being monitored and collects data that is then supplied to the connected Spotlight clients. The Diagnostic Server automatically creates connections to the selected SQL Servers on the network. Connection information is saved so that it is available each time Spotlight is run. The Diagnostic Server collects data regardless of whether a Spotlight client is connected. As data is collected only once, there is no unnecessary replication of data. Data is evaluated on the Diagnostic Server so that all Spotlight clients receive consistent information about the instances being monitored. Note: The Diagnostic Server is a Windows service. This version of Spotlight on SQL Server is designed to monitor a maximum of 100 SQL Server or Analysis Services or Replication instances and 100 Windows servers. Monitoring more than this recommended limit may result in poor performance or product instability. Deployment Scenarios Scenario 1: Monitor 1 25 SQL Server instances When monitoring between one and 25 SQL Server instances you can install the Diagnostic Server (A), the playback database (B), and the Spotlight Statistics Repository (C) on the same

9 Deployment Guidelines 9 machine, as long as that machine meets the minimum hardware requirements listed in the Spotlight on SQL Server release notes. Scenario 2: Monitor SQL Server instances When monitoring between 25 and 100 SQL Server instances it is recommended that the Diagnostic Server (A) is placed on a different machine to the playback database (B) and Spotlight Statistics Repository (C). The machine(s) that host the playback database (B) and the Spotlight Statistics Repository (C) should be configured with an appropriate amount of I/O bandwidth to meet demand. Note: This deployment model assumes servers with directly attached storage. If your environment uses a storage area network (SAN) it may be possible to install the Spotlight Statistics Repository and the playback database on the same server.

10 Deployment Guidelines 10 Co-existence with Performance Analysis If you are using Spotlight on SQL Server and Performance Analysis, observe the following. Spotlight on SQL Server and Performance Analysis (middleware) must be on separate disk volumes. This prevents out of disk space conditions which may affect monitoring. Spotlight on SQL Server and Performance Analysis repositories can co-exist in scenario two provided the hardware specifications of the machine that the repositories are installed on are adequate. Spotlight on SQL Server and Windows domains If the Diagnostic Server is in a different domain to the SQL Servers it is monitoring and you want to use Windows Authentication when the Diagnostic Server is connecting to these servers, the domain that the Diagnostic Server account resides in must be trusted by the Domain that the SQL Servers are in. Enterprise Edition - If the Diagnostic Server is in a different domain to the domain that the Spotlight clients are in, the domain that the Diagnostic Server is in must trust the domain that the Spotlight Client users are in. Spotlight on SQL Server and Firewalls Running Spotlight on SQL Server in an environment with a firewall may require ports to be opened between the Diagnostic Server and the monitored SQL Servers, or ports to be opened between the Diagnostic Server and the Spotlight clients. If the firewall is on the same machine as the diagnostic server When a software firewall is installed on the same machine as the diagnostic server, ensure the following port is open on the firewall. Spotlight on SQL Server Enterprise Edition Desktop Edition Open this port on the firewall. TCP 3166 TCP 7981

11 Deployment Guidelines 11 If the diagnostic server and monitored SQL Servers are inside the DMZ Note: This feature is not available in the Desktop Edition. The Spotlight client communicates with the Diagnostic Server using port 3843 TCP and UDP. These ports need to be opened on the firewall. If the diagnostic server is outside the DMZ; the monitored SQL Servers are inside the DMZ Notes: In Spotlight on SQL Server Desktop Edition the UDP and TCP ports between the Spotlight client and Diagnostic server are To locate a SQL Server instance by port number, open port 1434 for UDP packets on the firewall. Allow the Out-of-process Collector through the firewall. For the Enterprise Edition, allow:..\diagnostic Server\Agent\ext\QuestOOPCollector.exe For the Desktop Edition, allow:..\spotlight on SQL Server Desktop\Diagnostic Server\Agent\ext\QuestDesktopCollector.exe

12 Deployment Guidelines 12 To setup Spotlight on SQL Server in your environment Step 1: SQL Server firewall connectivity Open ports as outlined in the Microsoft KBase article that describes SQL Server firewall connectivity issues. Step 2: WMI Ports Windows WMI uses the RPC and DCOM subsystems in Windows. The ports that are used in WMI are auto-negotiated between hosts. In order to effectively use WMI between fire walled hosts, you can limit the number of ports used by the DCOM subsystem and only open those ports. The following outlines instructions to limit the number of ports that DCOM will use: 1. Open regedt32.exe 2. Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc 3. If there is no subkey titled "Internet", create one. 4. Inside the Internet key, create a REG_MULTI_SZ value named "Ports". Each line of the Ports value should specify a range of ports available to DCOM. For this example, add a single line that reads " ". 5. Add a new REG_SZ value named "PortsInternetAvailable", set it to "Y" 6. Add a new REG_SZ value named "UseInternetPorts", set it to "Y" 7. Open up TCP port 135 to internal traffic. (It may also be necessary to open up UDP 135) 8. Open up the DCOM port range (e.g ) to internal traffic. See the following link for more information:

13 3 Size Requirements Diagnostic Server 300 MB If the Diagnostic Server s connection to the Spotlight Statistics Repository or playback database is interrupted, the Diagnostic Server will cache data to the local disk. In this event, an extra 2 MB per hour, per monitored SQL Server is required. Spotlight Client 200 MB This space should exist on a local disk drive rather than a network drive. Spotlight Statistics Repository Note: This feature is not available in the Desktop Edition. Approximately 1.2 GB for each monitored SQL Server instance and the corresponding monitored Windows host on which the SQL Server instance resides. This estimate assumes default configuration in an average environment. Actual space used will depend on your environment and any data collection/storage configuration changes that are made. For more information, see the Spotlight on SQL Server Sizing Wizard. You can access the wizard from the Spotlight Installation Center. Playback Database Enterprise Edition Requires approximately 270 MB for each monitored SQL Server instance and the corresponding monitored Windows host on which the SQL Server instance resides. Retains 7 days of historical data for each connection in the playback database by default. This is configurable. Desktop Edition Requires approximately 6 MB for each monitored SQL Server instance and the corresponding monitored Windows host on which the SQL Server instance resides. Retains 4 hours of historical data for each connection in the playback database. (non configurable)

14 Size Requirements 14 Assumes default configuration in an average environment. Actual space used will depend on your environment and any data collection/storage configuration changes that are made. For more information see the Spotlight on SQL Server Sizing Wizard. You can access the wizard from the Spotlight Installation Center.

15 4 Permissions and Requirements Diagnostic Server Machine Permissions During installation If the Diagnostic Server user does not have privileges to start services, that privilege is granted by Spotlight during the installation process, if possible. During operation During operation the Diagnostic Server requires write access to the following folder: C:\Program Files The minimum Windows privilege level required to run the Diagnostic Server is Power User. Spotlight on SQL Server requires that the Diagnostic Server have the following permissions to successfully connect to a SQL Server instance. This information is specified when a new Windows or SQL Server instance is configured through the Spotlight Connection Manager or Spotlight Enterprise View. SQL Server permissions required on the Diagnostic Server Each SQL Server connection from the Diagnostic Server must have access to a SQL Server account that is a member of the sysadmin server role. This can be a SQL Server login (such as 'sa'), or the Diagnostic Server can be installed to run under a Windows account that is trusted by SQL Server. Also, the data must be retrievable over your network. Spotlight on SQL Server requires more than just a port 1433 TCP/IP connection to SQL Server to do this. Spotlight on SQL Server Enterprise Edition Desktop Edition Default port for retrieving data on the network. This port must be open on the Diagnostic server. Default port for the data collection subsystem of the Diagnostic server. No external connections are required on this port

16 Permissions and Requirements 16 Note: See "Spotlight on SQL Server and Firewalls" (page 10) for more information on running Spotlight on SQL Server in an environment with firewalls. Windows permissions required on the Diagnostic Server To retrieve performance counter information, the Diagnostic Server executes WMI queries against the Windows server on which SQL Server is currently running. To do this, the Diagnostic Server needs to have access to a Windows account that can retrieve this information. This account will normally be a member of the Administrators group on the server. If you do not have access to an Administrator account, have your Windows administrator assign you the required permissions on the server. Note: To monitor the Windows machine that hosts the Diagnostic Server, Windows requires that the Spotlight connection use Windows authentication. When creating a Windows connection to the Diagnostic Server machine, select the Use Diagnostic Server credentials option.

17 Permissions and Requirements 17 Requirements Platform Memory Hard Disk Space Operating System Additional Software 2 GHz Pentium Dual Core 2 GB RAM 300 MB If the Diagnostic Server s connection to the Spotlight Statistics Repository or playback database is interrupted, the Diagnostic Server will cache data to the local disk. In this event, an extra 2 MB per hour, per monitored server is required. Microsoft Windows XP Service Pack 2 or later (32-bit and 64-bit) Microsoft Windows Server 2003 (32-bit and 64-bit) Microsoft Windows Server 2008 (32-bit and 64-bit) Microsoft Windows Server 2008 R2 (64-bit) Microsoft Windows 7 (32-bit and 64-bit).NET 3.5 or later must be installed on the Diagnostic Server machine. SQL Server Client Tools To use the Discovery Wizard to locate SQL Servers on your network the SQL Server Client Tools must be installed on the Diagnostic Server. The SQL Server Client Tools are on the installation disk for Microsoft SQL Server 2000, 2005, and To use Spotlight on Analysis Services the Client Connectivity tools must be installed. SQL Server Management Tools To use Spotlight on Analysis Services, Spotlight on SQL Server Replication, and Session Trace and SQL Analysis in Spotlight on SQL Server, SQL Server Management Tools must be installed on the Diagnostic Server. The SQL Server Management Tools are available from any SQL Server 2005 or SQL Server 2008 edition except SQL Server Express and SQL Server Compact. The version required corresponds to the latest version of SQL Server that you are monitoring. Note, if you are monitoring SQL Server 2000 servers, you need the Management Tools from SQL Server Update the Quest Diagnostic User Groups During installation, Spotlight creates the following local user groups on the diagnostic server. Group Quest Description Members of this group are granted user privileges to the Diagnostic Server. They can do the usual diagnostic tasks. For example, they can

18 Permissions and Requirements 18 Group Diagnostic Users Quest Diagnostic Administrators Quest Diagnostic Read-Only Description view the home page, the drilldown pages, browse the playback data and change alarm thresholds. Members of this group are granted administrator privileges in addition to user privileges. They can kill database sessions and change sensitive configuration items. Note: Administrative changes are logged. The logged entry includes the date, time, connection name, user and client IP address, a brief description of the action, and whether it succeeded or not. The log file is:..\diagnostic Server\Agent\log\admin-audit.log Members of this group can view the home page, the drilldown pages, the playback data and alarm cases. They cannot make changes to Spotlight's operation. For example, they cannot change the Diagnostic Server and Monitored Servers. How do I become a member of the Quest Diagnostic User Groups? Your Network Administrator adds members to the Quest Diagnostic User groups as required. Members can be Windows users or Windows domain groups. Aliases are not supported. The Windows user on the Spotlight client machine that installed the Diagnostic Server is automatically added to all groups. What if I am not a member of a Quest Diagnostic User Group? Contact your Network Administrator. You need to be a member of at least one Quest Diagnostic User Group to connect your Spotlight on SQL Server client to the diagnostic server. What if I want to increase my level of membership? Contact your Network Administrator. The privileges available to you corresponds to the highest Quest Diagnostic User group you are a member of. Quest Diagnostic Read-Only users have the fewest privileges, but if you are also a member of the Quest Diagnostic Administrators group then you will have administrator privileges. Note: Any change to a user s role by modifying these Windows groups will not take effect until that user restarts their Spotlight client and it reconnects to the Diagnostic Server. For this reason, it is recommended that the Diagnostic Server be restarted if the role changes need to take immediate effect. Using Spotlight These tables provide information on the levels of service available to the various user groups.

19 Permissions and Requirements 19 Note: Some of these icons, particularly those on the Configure Ribbon Tab, have multiple access locations. For example, you can open the Project Lucy icon from the Configure Ribbon Tab or the Project Lucy Ribbon Tab. The level of service available to the user group is the same, no matter where the icon is opened from. Configure Ribbon Tab Administrator User Readonly Connections Add/Delete connection profiles Enable/Disable monitoring connections Yes Yes No Yes Yes No Configure Yes Yes No Alarms Ignore Yes Yes No Run a program when a threshold is reached Yes No No Yes Yes No Scheduling SQL Analysis SQL Server Response Time Custom Counters Error Log Entries Yes Yes No Yes No No Yes Yes No Yes Yes No

20 Permissions and Requirements 20 Configure Ribbon Tab Administrator User Readonly Monitored Files Yes Yes No Appearance Yes Yes Yes Spotlight Assistance Yes Yes Yes Start-up Yes Yes Yes Troubleshooting Yes Yes Yes Diagnostic Server Project Lucy Change the Diagnostic Server address Configure the mail server used by the Diagnostic Server Configure the maintenance schedule for the Playback and Spotlight Statistics Repository databases Configure the Playback database Configure the Spotlight Statistics Repository Configure Uploading data to Project Lucy Specify the location of your Web Reports server Configure Uploading data to Project Lucy Yes Yes Yes Yes Yes No Yes Yes No Yes Yes No Yes Yes No Yes Yes No Yes Yes No Yes Yes No Monitor Alarms Action Administrator User Readonly Snooze Alarm Yes Yes No

21 Permissions and Requirements 21 Monitor Alarms Action Administrator User Readonly Ignore Alarm Yes Yes No Monitor SQL Server Drilldowns Administrator User Readonly Memory Buffer Cache Clear Cache Procedure Cache Clear Cache SQL Activity Sessions Kill Session Yes No No Yes No No Yes No No Databases Support Services Indexes Update Statistics SQL Agent Jobs Start Job Yes No No Yes No No Service Status Start / Stop Service Cluster Services Take Offline Cluster Services Bring Online Cluster Services Move Group Yes No No Yes No No Configuration Change parameter Yes No No Error Log Cycle Error log Yes No No

22 Permissions and Requirements 22 Monitor Windows Drilldowns Administrator User Readonly Processes Processes Terminate Yes No No Services Start Services Stop Services Pause Services Resume Yes No No Spotlight Client Machine Permissions During installation During installation, Spotlight requires write access to the following folders: The Spotlight installation folder Default for Spotlight on SQL Server Enterprise Edition:..\Quest Software\Spotlight on SQL Server Default for Spotlight on SQL Server Desktop Edition:..\Quest Software\Spotlight on SQL Server Desktop C:\Program Files\Common Files\Quest Shared Windows XP / Windows 2003 Server C:\Documents and Settings\All Users\Application Data\Quest Software\Spotlight Windows Vista / Windows 2008 Server / Windows 7 C:\ProgramData\Quest Software\Spotlight and to the following Windows registry keys and sub-keys: HKEY_LOCAL_MACHINE\SOFTWARE\Quest Software\Products HKEY_LOCAL_MACHINE\SOFTWARE\Quest Software\Spotlight HKEY_CLASSES_ROOT In many cases, the Spotlight installer will run at elevated privileges in order to perform the required actions. These privileges can specifically be allowed or disallowed by system administrators by means of standard Microsoft Installer (MSI) policy settings.

23 Permissions and Requirements 23 If multiple users of a system install Spotlight for use, the additional users must be local administrators. During operation During operation, Spotlight requires write access to the following file locations: Windows XP / Windows 2003 Server C:\Documents and Settings\All Users\Application Data\Quest Software\Spotlight C:\Documents and Settings\All Users\Application Data\Quest Software\Shared C:\Documents and Settings\<current user>\application Data\Quest Software\Spotlight Windows Vista / Windows 2008 Server / Windows 7 C:\ProgramData\Quest Software\Spotlight C:\ProgramData\Quest Software\Shared C:\Users\<current user>\appdata\roaming\quest Software

24 Permissions and Requirements 24 Requirements Platform Memory Hard Disk Space Operating System Additional Software 1 GHz Pentium 4 PC 1 GB RAM 200 MB This space should exist on a local disk drive rather than a network drive. Microsoft Windows XP Service Pack 2 or later (32-bit and 64-bit) Microsoft Windows Server 2003 (32-bit and 64-bit) Microsoft Windows Server 2008 (32-bit and 64-bit) Microsoft Windows Server 2008 R2 (64-bit) Microsoft Windows Vista (32-bit and 64-bit) Microsoft Windows 7 (32-bit and 64-bit) SQL Server Client Tools To use the Discovery Wizard to locate SQL Servers on your network the SQL Server Client Tools must be installed. The SQL Server Client Tools are on the installation disk for Microsoft SQL Server 2000, 2005, and To use Spotlight on Analysis Services the Client Connectivity tools must be installed. Install.NET 2.0 or later To use the Spotlight Report Viewer,.NET 2.0 or later must be installed on the Spotlight client machine. Microsoft Internet Explorer 6.0 or later. Microsoft Data Access Components (MDAC) MDAC includes the ODBC and other components that enable a connection to be established to a SQL Server database. The database may be local or remote. Your client machine must have MDAC 2.7 (or later) installed. MDAC is available from the Microsoft website: To find out the version of MDAC that you are currently running, you can download an application from the Microsoft website called the Component Checker Tool. Review the following Microsoft Knowledge Base article for more information: Other Requirements CD-ROM drive or Internet connection (required for installation only). A monitor capable of supporting a resolution of 1280 x1024 or greater.

25 Permissions and Requirements 25 SQL Server Machine Permissions See "SQL Server permissions required on the Diagnostic Server" (page 15) for more information. Virtualization Note: This feature is not available in the Desktop Edition. For Spotlight to monitor a VMware server, the username specified must have at least a read-only role for the ESX server or VirtualCenter server that you want to connect to.

26 Permissions and Requirements 26 Requirements SQL Server Database Cloud Service Operating Systems Virtualization Connection Limit Spotlight can diagnose SQL Server instances of the following versions: SQL Server 2000 (Service Pack 3 or later) SQL Server 2005 (32-bit and 64-bit) SQL Server 2008 (32-bit and 64-bit) SQL Server 2008 R2 (32-bit and 64-bit) Spotlight on SQL Server also supports MSDE (2000), SQL Express (2005) and SQL Server 2008 Express Edition. Note that use of these versions to host playback or Spotlight Statistics Repository databases is not supported. Spotlight cannot diagnose earlier versions of SQL Server (version 7.x and earlier). Spotlight supports all SQL Server sort orders, including case-sensitive and binary sort orders. Spotlight cannot connect to SQL Server instances where the instance name contains non-us ASCII characters. Spotlight supports SQL Azure. Spotlight can diagnose the following operating systems: Microsoft Windows Server 2003 (32-bit and 64-bit) Microsoft Windows Server 2008 (32-bit and 64-bit) Microsoft Windows Server 2008 R2 (64-bit) Microsoft Windows XP (32-bit and 64-bit) Microsoft Windows Vista (32-bit and 64-bit) Microsoft Windows 7 (32-bit and 64-bit) Note: On each monitored instance, Spotlight requires the network setting "File and Print Sharing" to be enabled and any firewall to be configured to: open port 1434 for UDP packets open the SQL Server TCP port (default is 1433) Spotlight on SQL Server can monitor virtual guest machines in a VMware ESX infrastructure. The following versions are supported: VMware vcenter 2.5 (or later) VMware ESX Server 4.0 (or later) This version of Spotlight on SQL Server is designed to monitor a maximum of 100 SQL Server, Analysis Services, or Replication instances and 100 Windows servers. Monitoring more than this recommended limit

27 Permissions and Requirements 27 may result in poor performance or product instability. Enable performance counters Spotlight on SQL Server uses the SQL Server virtual table sysperfinfo (SQL Server 2000) and sys.dm_os_performance_counters (SQL Server 2005 and 2008) to retrieve data for many of its displays. In some rare cases, this table may not contain information. When this is the case, Spotlight on SQL Server will not be able to collect the data it requires, and will display "0" for many of its components. Most obvious will be the Memory icons on the home page, which will show 0 MB of memory used by SQL Server. Also, many of the flows on the home page will show no activity, and many drilldowns will show incomplete information. Spotlight on SQL Server raises an informational alarm shortly after connecting if it detects that the sysperfinfo or sys.dm_os_performance_counters table contains no data. You can confirm the existence of this problem by running the following SQL in Query Analyzer for SQL Server 2000: select * from master..sysperfinfo or by running the following SQL in SQL Server Management Studio for SQL Server 2005 and 2008: select * from sys.dm_os_performance_counters If this query returns no records, then your SQL Server performance counters are missing and Spotlight on SQL Server will not be able to operate correctly. Sometimes, for a variety of reasons, the SQL Server Performance Monitor counters will not show up as they should. Often, but not always, this problem can be fixed by following these steps. To enable performance counters 1. At the command prompt, type the following: unlodctr.exe MSSQLServer 2. Then type: lodctr.exe <SQL Server path>\binn\sqlctr.ini 3. Reboot the server. More information can be found in the SQL Server Knowledge Base at Enable disk counters Spotlight on SQL Server cannot display some disk information properly unless the machine being monitored has disk performance counters enabled. This affects the Disk Activity component on the home page, various I/O charts on the SQL I/O Activity tab and Windows Activities drilldowns, and disk graphs on the Databases drilldown.

28 Permissions and Requirements 28 Spotlight on SQL Server raises the Disk Counters alarm if it detects that disk counters are not enabled on the machine being monitored. To enable disk data collection 1. Start a command line window on the server machine. 2. Type the following at the command prompt: diskperf -y 3. Restart the machine. Spotlight Statistics Repository Note: This feature is not available in the Desktop Edition.

29 Permissions and Requirements 29 Requirements Database sizing Hard Disk Space Recommended SQL Server version Other Requirements Maintenance By default, the size of the Spotlight Statistics Repository is set to 1000MB (data size) and 250MB (log size). These sizes are flexible and can be changed by running the Spotlight Statistics Repository creation script. The script is located in the install directory as follows:..\plug-ins\diagnostics Server\Scripts Approximately 1.2 GB for each monitored SQL Server instance and the corresponding monitored Windows host on which the SQL Server instance resides. This estimate assumes default configuration in an average environment. Actual space used will depend on your environment and any data collection/storage configuration changes that are made. For more information, see the Spotlight on SQL Server Sizing Wizard. You can access the wizard from the Spotlight Installation Center. To use Spotlight Reporting and Trending, it is recommended that the Spotlight Statistics Repository is installed on SQL Server 2005 or SQL Server Installing the Spotlight Statistics Repository on SQL Server 2011 (Denali) CTP1 or CTP2 is not supported. Installing the Spotlight Statistics Repository on SQL Server 2000 can result in errors being displayed and no data being shown in some views. Installing the Spotlight Statistics Repository on SQL Server 2000 is not recommended. Note: Due to the size of the Spotlight Statistics Repository, it is recommended that this database is not installed on a SQL Express instance. The SQL Browser service must be running on the machine where the Spotlight Statistics Repository is installed. Alternatively you can use the host and port number of the (named) SQL Server instance you want to connect to, when creating a connection and connecting to the Spotlight Statistics Repository. Use the following syntax: HOST,PORT Where HOST is the machine name and PORT is the port for the (named) SQL Server instance. See "Configure the Spotlight Statistics Repository" (page 41) for more information. The TCP protocol must be enabled on the instance where the Spotlight Statistics Repository resides. By default, the Diagnostic Server runs maintenance procedures daily at

30 Permissions and Requirements 30 3am for the Spotlight Statistics Repository. It is highly recommended that regular maintenance is performed on the Spotlight Statistics Repository. The recommended maintenance plan is outlined in the online help and in this guide. See "Maintenance Plan for Spotlight Statistics Repository and Playback Database" (page 31) for more information. Playback Database Note: This feature has limited support in the Desktop Edition. A maximum of four hours playback data is available. Scheduling cannot be configured. Requirements Database sizing Hard Disk Space Recommended SQL Server version Other Requirements Maintenance By default, the size of the playback database is set to 500MB (data size) and 125MB (log size). See "Playback Database" (page 13) for more information. Installing the playback database on SQL Server 2011 (Denali) CTP1 or CTP2 is not supported. Due to the size of the playback database, it is recommended that this database is not installed on a SQL Express instance. The SQL Browser service must be running on the machine where the playback database is installed. Alternatively you can use the host and port number of the (named) SQL Server instance you want to connect to, when creating a connection and connecting to the playback database. Use the following syntax: HOST,PORT Where HOST is the machine name and PORT is the port for the (named) SQL Server instance. See "Configure the Spotlight Statistics Repository" (page 41) for more information. The TCP protocol must be enabled on the instance where the playback database resides. By default, the Diagnostic Server runs maintenance procedures daily at 3am for the playback database. It is highly recommended that regular maintenance is performed on the playback database. The recommended maintenance plan is outlined in the online help and in this guide. See "Maintenance Plan for Spotlight Statistics Repository and Playback Database" (page 31) for more information.

31 Permissions and Requirements 31 Maintenance Plan for Spotlight Statistics Repository and Playback Database It is recommended that a maintenance plan for both the Spotlight Statistics Repository and the playback database is implemented. Both the Spotlight Statistics Repository and playback database support a large number of monitored servers and automatically maintain the age of data available. Due to the nature of the automatic purging of old data, the data may become fragmented and this may decrease the efficiency of data retrieval operations over time. This topic provides guidance on how to configure and automate the maintenance of the Spotlight Statistics Repository and the playback database. Database Configuration The Spotlight Statistics Repository and the playback database do not require the database to be run under the Full Recovery model. However, since Spotlight uses the model system database to create the repository, your Spotlight repository may inherit the Full Recovery setting. Unless you are required to use the Full Recovery model and are prepared to perform regularly scheduled log file backups, we recommend you change the repository recovery model to Simple (in SQL Server 2000, this option is called Truncate Log on Checkpoint). Doing so will help maintain a considerably smaller transaction log file. To change the repository database to Simple recovery, run the following command: SQL Server 2000 EXEC [dbo].[sp_dboption] 'SpotlightStatisticsRepository','trunc. log on chkpt.','true' SQL Server 2005 and 2008 ALTER DATABASE [SpotlightStatisticsRepository] SET RECOVERY SIMPLE; Fragmentation and Index Performance The Spotlight Statistics Repository implements a star schema because of the data warehousingstyle simplicity it offers for data storage and retrieval. The star schema implements a primary fact table that references a number of dimension tables. The fact table holds collections and alarm data, and the dimension tables hold definition information on everything from instance information to collection names. Spotlight maintains the age of the data in the repository, but the continuous INSERT and DELETE operations performed for data insertion and purging can lead to fragmentation. Fragmentation will eventually lead to increased CPU and I/O resource consumption.

32 Permissions and Requirements 32 Although the playback database uses a simpler schema, its data will also become fragmented over time as new data is inserted and old data purged. To best address performance concerns, fragmentation should be minimized and index statistics should be kept up-to-date. Spotlight's scheduled maintenance feature does this automatically. By default, the Diagnostic Server runs maintenance procedures daily at 3am for the playback database and Spotlight Statistics Repository. The maintenance schedule can be changed in Spotlight Options. See the online help for more information. Database Backup The Spotlight Statistics Repository and playback database should be included in the list of important databases which have a disaster recovery plan associated with them. The implementation of this task is dependent on the policies and infrastructure of your organization.

33 5 Installation and Upgrade Enterprise Edition Install Enterprise Edition 1. Complete the Deployment Checklist (page 6). 2. Run the Spotlight on SQL Server Enterprise Edition installation executable. Stages of Installation Spotlight Components Diagnostic Server Diagnostic Server Users Playback Database Description Install the Spotlight client or the Diagnostic server or both. The Spotlight client will be installed on this computer. The Diagnostic server can be installed on this computer or another computer on the network. Select to install the diagnostic server on this computer or another computer on the network. Specify the user details for the account under which the Diagnostic Server will run. Select from a domain user account or a local system account. Notes: When installing the Diagnostic Server, Windows administrator privileges are required to register the Diagnostic Server as a Windows service and to create the Windows user groups that are used to authenticate Spotlight clients. When installing on a remote machine, the Windows account on the Spotlight client must have Windows administrator privileges on the target Diagnostic Server host. The local computer must be able to authenticate this user. If you are installing the Diagnostic Server on a remote machine, ensure the user credentials entered have Windows administrator privileges on the target Diagnostic Server host and can be authenticated on the Spotlight client machine. The user is added to all Quest Diagnostic User Groups. If the user does not have privileges to start services the required privileges are granted by the Spotlight on SQL Server installation process. Add to the Quest Diagnostic User Groups if required. See "Update the Quest Diagnostic User Groups" (page 17) for more information. The Playback database can be on the same machine as the Spotlight client

34 Installation and Upgrade 34 Stages of Installation Description and Diagnostic server or a different machine. In the Instance field select the machine to install the playback database on. Select Windows or SQL server authentication. In the database field, optionally rename the database. The default name is SpotlightPlaybackDatabase. If the database has not already been created, click Create to create the database. Default Installation Folders Default for the Diagnostic Server:..\Quest Software\Diagnostic Server Default for the Spotlight client:..\quest Software\Spotlight on SQL Server Desktop Notes: Do not install Spotlight on SQL Server Enterprise Edition into an existing Spotlight Console directory. If the Spotlight on SQL Server Desktop Edition is already installed on the system then you must change the default installation path. The default installation path will show as the installation path of the Desktop edition, typically..\quest Software\Spotlight on SQL Server Desktop and this must be changed. If you install a different Spotlight after you have installed Spotlight on SQL Server Enterprise Edition, do not install the new Spotlight in the Spotlight on SQL Server directory. Upgrade Enterprise Edition Upgrade Procedure The following information on the Diagnostic Server is preserved when you upgrade: Connection properties for all monitored servers (including changes to scheduling and alarms) Enterprise views Collection properties notification configuration for alarms Global options such as user-created Error Log rules Configuration information for the Spotlight Statistics Repository (this applies only if you installed the Spotlight Statistics Repository from an earlier version of Spotlight on SQL Server) and the playback database.

35 Installation and Upgrade 35 To upgrade Spotlight on SQL Server Notes: 1. Back up the Agent directory on the Diagnostic Server. Like any software upgrade, it is recommended that you back up important Spotlight data before beginning the upgrade process. The default location of the Agent directory is:..\quest Software\Diagnostic Server\Agent 2. On the Spotlight client machine, run the Spotlight on SQL Server executable. The playback database and Spotlight Statistics Repository are upgraded automatically. If the Spotlight client and Diagnostic Server are running different versions of Spotlight on SQL Server, the client will be unable to connect to the Diagnostic Server. You can upgrade only from Spotlight on SQL Server Enterprise 8.0 or 7.6. If you are using an earlier version of Spotlight, upgrade to 7.6 before upgrading to 8.1. Spotlight on SQL Server Enterprise Edition and Desktop Edition are separate products. You cannot upgrade from Spotlight on SQL Server Desktop Edition to Spotlight on SQL Server Enterprise Edition. Start and Stop the Diagnostic Server The Diagnostic Server is a Windows service and can be started and stopped via the Windows Control Panel or the Run command from the Start menu. Note: If you attempt to stop the Diagnostic Server whilst a program or command line action that runs in response to an alarm is still executing, the Diagnostic Server will wait until that program or command line action has ended before stopping. To start or stop the Diagnostic Server 1. On the Diagnostic Server machine, open Windows Control Panel. 2. Click Administrative Tools Services. 3. From the list of available services, double click on the Diagnostic Server name as follows: Enterprise Edition - Quest Diagnostic Server (by default). Desktop Edition - Quest Diagnostic Server Desktop. 4. Click Start to start the Diagnostic Server. Click Stop to stop the service. Uninstall Enterprise Edition Uninstall all Diagnostic server(s) before you uninstall the Spotlight client(s). In Spotlight on SQL Server Enterprise Edition multiple Diagnostic servers, Spotlight clients and machines may be involved.

36 Installation and Upgrade 36 To uninstall Spotlight on SQL Server Enterprise Edition 1. Open Windows Control Panel. 2. Windows XP - Select Add or Remove Programs Windows Vista / Windows 7 - Select Programs and Features 3. Select the Diagnostic server and click Remove to uninstall the Diagnostic server. Notes: The default name for the diagnostic server is - Quest Diagnostic Server Repeat this step until all diagnostic servers used by Spotlight on SQL Server Enterprise Edition are removed. A running Diagnostic Server is automatically shut down before being uninstalled. 4. Select Spotlight on SQL Server and click Remove to uninstall the Spotlight on SQL Server client. Note: The client need not be on the same machine as the Diagnostic server(s). There may be multiple clients. Uninstall all clients. Desktop Edition Install Desktop Edition 1. Complete the Deployment Checklist (page 6). 2. Run the Spotlight on SQL Server Desktop Edition installation executable. Stages of Installation Configure the Diagnostic Server Description Specify the user details for the account under which the Diagnostic Server will run. Select from a domain user account or a local system account. Notes: When installing the Diagnostic Server, Windows administrator privileges are required to register the Diagnostic Server as a Windows service and to create the Windows user groups that are used to authenticate Spotlight clients. If the user does not have privileges to start services the required privileges are granted by the Spotlight on SQL Server installation process.

37 Installation and Upgrade 37 Stages of Installation Configure the Playback Database Installation Folders Description The Playback database can be on the same machine as the Spotlight client and Diagnostic server or a different machine. In the Instance field select the machine to install the playback database on. Select Windows or SQL server authentication. In the database field, optionally rename the database. The default name is SpotlightPlaybackDatabase. If the database has not already been created, click Create to create the database. Default for the Spotlight client:..\quest Software\Spotlight on SQL Server Desktop The Diagnostic Server is installed in the Diagnostic Server sub-directory of the client installation folder. This is not configurable. Notes: Do not install Spotlight on SQL Server Desktop Edition into an existing Spotlight Console directory. If you install a different Spotlight after you have installed Spotlight on SQL Server Desktop Edition, do not install the new Spotlight in the Spotlight on SQL Server Desktop directory. Upgrade Desktop Edition The following information on the Diagnostic Server is preserved when you upgrade: Connection properties for all monitored servers (including changes to alarms) Enterprise views To upgrade Spotlight on SQL Server 1. Back up the Agent directory on the Diagnostic Server. Like any software upgrade, it is recommended that you back up important Spotlight data before beginning the upgrade process. The default location of the Agent directory is:..\quest Software\Spotlight on SQL Server Desktop\Diagnostic Server\Agent 2. On the Spotlight client machine, run the Spotlight on SQL Server executable. Note: Spotlight on SQL Server Enterprise Edition and Desktop Edition are separate products. You cannot use this procedure to upgrade from Spotlight on SQL Server Desktop Edition to Spotlight on SQL Server Enterprise Edition.

38 Installation and Upgrade 38 Uninstall Desktop Edition Uninstall the Diagnostic server before you uninstall the Spotlight client. In Spotlight on SQL Server Desktop Edition there is one Diagnostic server and one Spotlight client and they are installed on the same machine. To uninstall Spotlight on SQL Server Desktop Edition 1. Open Windows Control Panel. 2. Windows XP - Select Add or Remove Programs Windows Vista / Windows 7 - Select Programs and Features 3. Select Quest Diagnostic Server Desktop and click Remove to uninstall the Diagnostic server. Note: A running Diagnostic Server is automatically shut down before being uninstalled. 4. Select Spotlight on SQL Server Desktop and click Remove to uninstall the Spotlight on SQL Server client.

39 6 Configure Use the Configure ribbon tab to set how Spotlight collects diagnostic information. The Configure Ribbon Tab Connections Alarms Scheduling SQL Analysis Filters SQL Description Manage the connections to be monitored. You can add connections, delete connections and change the properties of connections. Modify the thresholds and severities that determine when alarms fire. Configure the actions to be taken when an alarm is raised. Configure how often the Diagnostic Server collects data for reporting and for when no Spotlight clients are connected. Note: This feature is not available in the Desktop Edition. Configure the filters used to gather SQL Analysis data. Note: Support of this feature is limited in the Desktop Edition. Declare the SQL statement for Spotlight to use to measure response time. Server Response Time Custom Counters Entries Files Error Log Monitored Create and configure Custom Counters. Declare the SQL error log entries for Spotlight to alarm on. Declare files whose size is to be monitored by Spotlight. Configure Spotlight appearance. Spotlight Configure the Diagnostic Server. Note: Support of this feature is limited in the Desktop Edition.

40 Configure 40 The Configure Ribbon Tab Description Diagnostic Server For more information on these configuration options, see the online help. Configure the Playback Database The playback database stores data recently collected by the Diagnostic Server. Storing playback data allows Spotlight to show both current and recent data and lets you replay the behavior of a Spotlight connection. Note: Each Diagnostic Server requires its own playback database. To store playback data 1. Click Configure Diagnostic Server. 2. Select Configure the playback database. 3. Complete the following: Option Instance Store playback data for n days Windows authentication Description Type or select the name of a SQL Server to host the playback database. Clicking the down arrow displays a list of available instances. Note: Due to the size of the playback database, it is recommended that the database is not installed on a SQL Express instance. Note: This feature is not available in the Desktop Edition. Specify the number of days you want Spotlight to store playback data. The number of days specified corresponds to the number of days of history available to view in the History Browser. The default is seven days. The minimum is two days. The maximum is 14 days. Select this option to connect to the playback database using the Diagnostic Server credentials, that is the credentials of the user logged in to the Spotlight client.

41 Configure 41 Option SQL Server authentication Database Create Description Select this option to connect to the playback database using SQL Server credentials and then complete the User and Password fields. User A valid user that enables Spotlight to connect to the instance hosting the playback database. Password The password required to connect the specified user to the instance hosting the playback database. The name of the playback database. The default database is SpotlightPlaybackDatabase. If you want your playback database to have a different name to the default, type a new name in the Database field before you click the Create button. To create a new playback database, click Create and enter the authentication details required to create the playback database. The authentication details must have permissions to create databases. Configure the Spotlight Statistics Repository Note: This feature is not available in the Desktop Edition. Spotlight uses a repository to store data archived from the Diagnostic Server. See "Requirements" (page 29) for more information on the disk space requirements of the Spotlight Statistics Repository. You can reduce the size of the repository by: Limiting the number of collections archived Reducing how often data is collected Reducing the data retention period. See "Schedule Data Collection" in the online help for information on the options that affect the size of the repository. You can install a new repository on any machine that has a SQL Server 2005 or SQL Server 2008 instance running, or select an existing data repository for the Diagnostic Server to use. Notes: Installing the Spotlight Statistics Repository on SQL Server 2000 can result in errors being displayed and no data being shown in some views. Installing the Spotlight Statistics Repository on SQL Server 2000 is not recommended. Due to the size of the Spotlight Statistics Repository, it is recommended that this database is not installed on a SQL Express instance.

42 Configure 42 To configure the Spotlight Statistics repository 1. Click Configure Diagnostic Server. 2. Select Configure the Spotlight Statistics Repository. 3. Complete the following options: Option Enable use of the Spotlight Statistics Repository Instance Windows authentication SQL Server authentication Database Create Description When this option is selected, Spotlight stores data in the Spotlight Statistics Repository for reporting purposes. Clear this option to stop storing data in the Spotlight Statistics Repository. This option must be selected to use Spotlight Reporting and Trending. Type or select the name of a SQL Server to host the Spotlight Statistics repository. Clicking the down arrow displays a list of available instances. Note: Due to the size of the Spotlight Statistics Repository, it is recommended that this database is not installed on a SQL Express instance. Select this option to connect to the repository using the Windows user name and password of the user logged in to the Spotlight client. Select this option to connect to the repository using SQL Server credentials. Complete the User and Password fields. User A valid user that enables Spotlight to connect to the instance hosting the Spotlight Statistics Repository. Password The password required to connect the specified user to the instance hosting the Spotlight Statistics Repository. Type the name of the database you are using as the Spotlight Statistics Repository. To create a new Spotlight Statistics Repository, type a name in the Database field and then click Create. To change the default name of the repository database or the location of the corresponding data and log files, click Configure repository data and log files. By default, the repository and data log files are created in the same location as those of the model database. Change the Diagnostic Server Address Note: This feature is not available in the Desktop Edition.

43 Configure 43 To change the Diagnostic Server address 1. Click Configure Diagnostic Server. 2. Select Change the Diagnostic Server address 3. In the Host field type or select the machine name where the Diagnostic Server is installed. Back Up Spotlight Configuration Data Spotlight configuration data is stored in the conf directory on the Diagnostic Server. You can perform backups of the Spotlight configuration data by backing up this directory regularly. Spotlight Edition Spotlight for SQL Server Enterprise Edition Spotlight for SQL Server Desktop Edition The default location for the conf directory..\quest Software\Diagnostic Server\Agent\conf..\Quest Software\Spotlight on SQL Server Desktop\Diagnostic Server\Agent\conf

44 Appendix: Contact Quest Contact Quest Support Quest Support is available to customers who have a trial version of a Quest product or who have purchased a Quest product and have a valid maintenance contract. Quest Support provides unlimited 24x7 access to SupportLink, our self-service portal. Visit SupportLink at From SupportLink, you can do the following: Retrieve thousands of solutions from our online Knowledgebase Download the latest releases and service packs Create, update and review Support cases View the Global Support Guide for a detailed explanation of support programs, online services, contact information, policies and procedures. The guide is available at: Spotlight Support When contacting Quest Support about a Spotlight product, please have the version and build number handy. You can obtain both by choosing the About option from the Help menu in the relevant Spotlight application. If your question is about an error message, write the message down and have it available for the technical support representative. Whenever you have a question about Spotlight, click Support Bundle or Contact Support on the Help menu. This creates a file called SpotlightSupport.zip. This file contains a snapshot of your Spotlight installation. Send this file and your request for assistance to Quest Software ([email protected]). Note: You can find SpotlightSupport.zip in different locations under different operating systems. Windows XP: C:\Documents and Settings\<user>\Application Data\Quest Software\Spotlight\Default\Support Vista: C:\Users\<user>\AppData\Roaming\Quest Software\Spotlight\Default\Support If you find that information in the Help system or printed user guides is incorrect, unclear, or incomplete, please report the problem to Quest Support.

45 Appendix: Contact Quest 45 Contact Quest Software Mail Web site Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA USA See our web site for regional and international office information. About Quest Software Now more than ever, organizations need to work smart and improve efficiency. Quest Software creates and supports smart systems management products helping our customers solve everyday IT challenges faster and easier. Visit more information.

46 Appendix: Third Party Contributions Spotlight on SQL Server contains some third party components (listed below). Copies of their licenses may be found at Component Blowfish v2 Cryptix License or Acknowledgement MIT. License may be found at Cryptix General License Copyright (c) The Cryptix Foundation Limited. All rights reserved. GDI+ 1 Mozilla Public License (MPL) Version 1.1 Indy Sockets Mozilla Public License (MPL) Version 1.1 Javamail Common Developer and Distribution License (CDDL) 1.0 Jaxan 1.1 Apache 1.1 JDOM JDOM 1.11 A copy of the source code is available from This product includes software developed by the Apache Software Foundation ( Copyright (C) Jason Hunter & Brett McLaughlin. All rights reserved. This product includes software developed by the JDOM Project ( JMock jmock Project License Copyright (c) , jmock.org All rights reserved. jregistry GNU Lesser General Public License 2.1 Copyright (C) 1991, 1999 Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA USA A copy of the source code is available from JUnit 4.7 Common Public License (CPL) 1.0 A copy of the source code is available from Jython 2.1 Jython 2.0, 2.1 License

47 Appendix: Third Party Contributions 47 Component License or Acknowledgement Copyright (c) 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007 Jython Developers All rights reserved. Log4J Apache License Version 1.1 Copyright (c) 2000 The Apache Software Foundation. All rights reserved. This product includes software developed by the Apache Software Foundation ( Log4Net Apache License Version 2.0 Copyright The Apache Software Foundation OpenSSL PicoContainer SharpZipLib 0.86 Simple Swingx Unicode SynEdit 1.0 OpenSSL License. Copyright (c) The OpenSSL Project. All rights reserved. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit ( BSD 4.4 Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. License may be found at GNU General Public License. License may be found at GNU LESSER GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. A copy of the source code is available from GNU LESSER GENERAL PUBLIC LICENSE Version 2.1, February 1999 Copyright (C) 1991, 1999 Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA USA A copy of the source code is available from Mozilla Public License (MPL) 1.1 ZipMaster 1.78 GNU Lesser General Public License 2.1 Copyright (C) 1991, 1999 Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA USA A copy of the source code is available from

48 Index A about Quest Software 45 architecture 7-8 B back up 43 C configuration data 43 configure Diagnostic Server 39 playback database 40 connections Diagnostic Server 42 Contact Quest Software 45 Customer support 44 D deployement scenarios 8 deployment checklist 6 Diagnostic Server address 42 configure 39 permissions 15 requirements 17 size requirements 13 start, stop 35 F firewalls 10 I install 33, 36 M maintenance plan 31 P permissions Diagnostic Server 15 Spotlight client 22 SQL Server 25 playback database configure 40 requirements 30 size requirements 13 Q Quest Software 45 Quest support 44 R requirements Diagnostic Server 17 playback database 30 Spotlight client 24 Spotlight Statistics Repository 29 SQL Server 26 DMZ 10

49 Index 49 S W size requirements windows domains 10 Diagnostic Server 13 playback database 13 Spotlight client 13 Spotlight Statistics Repository 13 Spotlight client permissions 22 requirements 24 size requirements 13 Spotlight Statistics Repository configure 41 install 41 maintenance plan 31 requirements 29 set up 41 size requirements 13 SQL Server permissions 25 SQL Server machine requirements 26 Support 44 T Technical support 44 U uninstall 35, 38 upgrade 34, 37