System requirements

SQL Server
performance
objects

The Microsoft SQL Servers you want to monitor must have the SQL Server performance objects installed and available to
BMC PATROL in order for all of the functions
in PATROL for Microsoft SQL Server to operate.

If PATROL for Microsoft SQL Server cannot find the SQL Server performance objects, it cannot configure the instance, and it generates the following message: 
The SQL Server performance objects are not available.If you cannot resolve this issue, refer to your SQLServer manual, see the Microsoft technical information website, or call Microsoft support.

Operating system and third-party support

Operating systems (32/64 bit, Standard/Enterprise edition, and clustered/non
clustered environment):

• Microsoft Windows Server 2003
• Microsoft Windows Server 2008
• Microsoft Windows Server 2012

Microsoft SQL Server: (32/64 bit, Standard/Enterprise edition, and clustered/non
clustered environment):

• Microsoft SQL Server 2005
• Microsoft SQL Server 2008
• Microsoft SQL Server 2012

BMC PATROL for Microsoft SQL Server can monitor any combination from this list, which is supported by Microsoft.

The list of versions of operating systems and Microsoft SQL Server supported by version 9.5.00 of BMC PATROL for Microsoft SQL Server.

PATROL Agent
and consoles

• BMC PATROL Agent version 9.0.00 or later
• BMC PATROL console version 3.5.90 or later
• BMC PATROL Central Operator – Web Edition version 7.7.70 or later
• BMC PATROL Central Operator – Microsoft Windows Edition version 7.7.70 or later
• BMC PATROL Console Server version 7.7.70 or later

PATROL Central consoles are not required, but a PATROL Agent is required for each monitored instance and a PATROL Console for UNIX or PATROL Console for Microsoft Windows is required to initially configure PATROL for Microsoft SQL Server.

Other BMC
PATROL products

• BMC PATROL for UNIX version 9.11.00
• BMC PATROL for Microsoft Windows version 4.5.00
• BMC PATROL Installation Utility version 7.5.62 or later

See Determining-the-version-of-the-installation-utility.

PATROL Cluster Configuration Wizard 1.5.20
(a component of PATROL for Microsoft Windows Servers)

PATROL Knowledge Module for Event Management 2.8.10

This product is required if you plan to monitor a clustered SQL Server. For more information, see Setting-up-PATROL-in-a-clustered-environment. For more information see Using-PATROL-Configuration-Manager-with-PATROL-for-Microsoft-SQL-Server

Distribution Server version 7.8 or later

You can use this product to distribute PATROL for Microsoft SQL Server throughout your enterprise.

Disk space
needed to install

40 MB are required to install on a computer
that is acting as a Managed System, Common System, and Console System

Fewer megabytes are required if you are installing only on a Managed System (37 MB), or only on a Console System (21 MB).

For more information about the roles that each computer performs, see Installing-for-the-first-time.

Browser

Netscape Navigator for UNIX and Red Hat Linux platforms

Install Netscape Navigator on the computer where the console resides.

Security levels

PATROL for Microsoft SQL Server can
operate at any of the security levels provided
by BMC PATROL

See Determining-the-PATROL-security-levels

License

You must have a valid demonstration license
(typically good for 30 days) or a permanent
license to run your BMC PATROL products.

If you do not have a permanent license, contact your BMC Software sales representative or the BMC Software
Contract Administration department for licensing information.

Installing into a UNIX environment without a browser

You must launch the installation utility from
the command line and use the -serveronly
command line option.

Accounts

PATROL Windows account

You must create a dedicated user account before BMC PATROL is installed. Use the
following guidelines:

• Stand-alone workgroup servers must use a local user account.
• Servers that are trusted members of a domain can use either a local or domain account.
• The account on a domain controller must be a member of the domain Administrators group.
• The PATROL account must be a member of the local Administrators group of the computer where the PATROL Agent resides.
• If you use a domain account, no local on that computer can have the same name.
• Do not use a built-in Administrator account.

PATROL UNIX account

• The account .login, .profile, .cshrc, and .kshrc files should not contain any customizations such as aliases, nondefault prompts, or unmask
  settings other than 022.
• Do not use the root account
• The account must have permission to create directories and write the installation logs to the $HOME and /tmp directories on the computer
  where you are installing products.
• The account must have access to a root account on the computer where BMC PATROL is installed.
• (recommended) Install BMC PATROL on local partitions. If BMC PATROL is installed on NFS-mounted partitions, the root account must have root access permissions on the NFS server.

PATROL requires the following accounts to monitor SQL Server:

• An SQL Server login account with system
  administrator privileges when standard
  security is selected
  or
  A Windows login account with system
  administrator (sa) privileges when
  integrated security is selected
• An SQL Server login account with user
  privileges

BMC PATROL automatically uses the appropriate login for each function. BMC PATROL uses the SQL Server or Windows account with system administrator privileges for the following functions:

• SQL Snapshot configuration
• DbStructureColl parameters
• LongRunningTrans parameters
• ProcedurecacheColl parameters

BMC PATROL uses the SQL Server user account for the following functions:

• All the parameters
• All other menu commands