Skip Headers
Oracle® Enterprise Manager System Monitoring Plug-in Installation Guide for Microsoft SQL Server
Release 12.1.0.5.0 for Windows

E35211-10
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

  PDF · Mobi · ePub

Oracle® Enterprise Manager

System Monitoring Plug-in Installation Guide for Microsoft SQL Server

Release 12.1.0.5.0 for Windows

E35211-10

September 2014

This document provides a brief description about the Oracle system monitoring plug-in for Microsoft SQL Server, details on the versions the plug-in supports, prerequisites for installing the plug-in, and step-by-step instructions on how to download, install, verify, and validate the plug-in.

The following topics are presented:

1 Description

The system monitoring plug-in for Microsoft SQL Server extends Oracle Enterprise Manager Cloud Control 12c to add support for managing Microsoft SQL Server instances. By deploying the plug-in within your Cloud Control environment, you gain the following management features:

  • Monitor SQL Server instances.

  • Supports both SQL Authentication and Windows Integrated Authentication

  • Gather configuration data and track configuration changes for SQL Server instances.

  • Raise alerts and violations based on thresholds set on monitored metrics and configuration data.

  • Provide rich out-of-box reports based on the gathered data.

  • Support monitoring by a local or remote Windows Agent. Local Windows Agent is an agent running on the same host as the Microsoft SQL Server. Remote Windows Agent is an agent running on a host that is different from the host where SQL Server is running.

  • Out-of-the-box monitoring templates for Microsoft SQL Server Cluster monitoring and Microsoft SQL Server AlwaysOn (HADR) monitoring.

  • Oracle Enterprise Manager Jobs are made easy-to-access by being accessible from the plug-in's UI. These jobs allow for the following management of Microsoft SQL Server:

    • Backup, restore, schedule, and naming of Microsoft SQL Server database backups.

    • Start, stop, pause, and resume of SQL Server Instances.

    • Killing of sessions that are high in CPU or memory usage.

2 What's New in This Release

This release of the Microsoft SQL Server Plug-in for OEM 12c includes many new features for better visibility into your Microsoft SQL Server environment. Highlighted below are some of the new features included in this release:

Added Support for Microsoft SQL Server 2014

Microsoft SQL Server Plug-in for OEM 12c supports a wide range of Microsoft SQL Server versions. This plug-in release adds support for the latest version of Microsoft SQL Server - SQL Server 2014. The plug-in supports not only standalone but also the cluster configuration of this version.

Monitoring of Microsoft SQL Server AlwaysOn Availability Groups

This version of the plug-in adds in support for Microsoft SQL Server's AlwaysOn Availability Groups. Configuring the plug-in to monitor an AlwaysOn Availability Group will allow the plug-in to gather information on availability databases, group names, group states, and much more. To see a full list of metrics gathered for the AlwaysOn Availability Groups, reference the Oracle Enterprise Manager System Monitoring Plug-in Metric Guide:

http://docs.oracle.com/cd/E24628_01/em.121/e51915/toc.htm

Updated User Interface

New to this version is also an all-new look and feel. Updated are the Home (Figure 1) and Analysis (Figure 2) pages, which contain new tables and metrics for better and quicker access the linked databases. Two new plug-in pages were added to visually display metrics covering the Microsoft SQL Server's performance (Figure 3) and metrics for each individual database (Figure 4) within the monitored instance.

Figure 1 Microsoft SQL Server Plug-in Home Page

Surrounding text describes Figure 1 .

Figure 2 Microsoft SQL Server Plug-in Analysis Page

Surrounding text describes Figure 2 .

Figure 3 Microsoft SQL Server Plug-in Performance Page

Surrounding text describes Figure 3 .

Figure 4 Microsoft SQL Server Plug-in Database Page

Surrounding text describes Figure 4 .

Backup and Restore Jobs for MS SQL Server Databases

Newly added this release, are jobs giving the management capabilities of creating and restoring database backups. With these new jobs, users are able to name the backup they are creating, schedule future backups, restore a previous backup, or delete a previous backup.

See Using the Backup and Restore Jobs for more information.

3 Supported Versions

This plug-in supports the following versions of products:

  • Enterprise Manager Cloud Control 12c Release 4 (12.1.0.4.0) or higher (Oracle Management Server and Oracle Management Agent).

  • Standard, Enterprise, and Workgroup editions of Microsoft SQL Server 2005, Microsoft SQL Server 2008, Microsoft SQL Server 2012, and Microsoft SQL Server 2014 as detailed below:

    • Microsoft SQL Server 2005 (32-bit or 64-bit).

    • Microsoft SQL Server 2008 (32-bit or 64-bit).

    • Microsoft SQL Server 2008 R2 (32-bit or 64-bit) including Failover Cluster support.

    • Microsoft SQL Server 2012 (32-bit or 64-bit) including Failover Cluster and AlwaysOn Availability Groups support.

    • Microsoft SQL Server 2014 (32-bit or 64-bit) including Failover Cluster and AlwaysOn Availability Groups support.

    Note:

    Monitoring of Microsoft SQL Server Clusters are only supported with a remote monitoring configuration. The Oracle Management Agent used in monitoring cannot be installed to one of the cluster nodes.

4 Prerequisites

The following prerequisites must be met before you can deploy the plug-in:

  • Enterprise Manager Cloud Control 12c Release 4 (12.1.0.4.0) or higher (Oracle Management Server and Oracle Management Agent) must be installed.

  • The plug-in is only supported when running the Oracle Management Agent on 32-bit or 64-bit Windows.

  • For the plug-in to establish connection to SQL Server instance using Windows Integrated Authentication (WIA) mode, when deployed on a 64-bit (x64 or IA64) copy of Oracle Management Agent running on 64-bit Windows operating system, do the following:

    • Obtain a copy of the required sqljdbc_auth.dll file from Microsoft. The sqljdbc_auth.dll file is available as part of Type 4 Microsoft SQL Server 2005 JDBC Driver version 3.0. After unzipping, you will find three files with same name, that is:

      auth\x86\sqljdbc_auth.dll
      auth\x64\sqljdbc_auth.dll
      auth\ia64\sqljdbc_auth.dll
      
    • Depending on the JVM version, copy the respective version of the sqljdbc_auth.dll file to the following location:

      Drive:\<agent_base>\plugins\oracle.em.smss.agent.plugin_12.1.0.5.0\dependencies\oracle.em.smss\jdbcdriver
      

      If the directory does not exist, then create it. The sqljdbc_auth.dll file should be copied directly under the folder specified. No sub-directories should be created.

    • When upgrading from previous versions of the Microsoft SQL Server plug-in, be sure to recreate the required folders and copy over the sqljdbc_auth.dll file to the new corresponding plug-in directory.

    • Type 4 Microsoft SQL Server 2005 JDBC Driver Version 4.0 is not currently supported for use with Windows Integrated Authentication.

    • No manual step needs to be performed when the plug-in is deployed on 32-bit copy of Oracle Management Agent (running on 32-bit or 64-bit Windows).

  • Access privileges required for non-admin System user to perform Remote Monitoring of SQL Server instance.

  • Windows Management Instrumentation Service is up and running.

  • Enable TCP/IP for the SQL Server instance. For more information, see Enabling and Finding TCP/IP Port Information.

  • Enable SQL or Mixed Authentication on the SQL Server instance. For more information, Enabling SQL Authentication or Mixed Authentication.

  • Create a suitable DB user with a sysadmin fixed server role. To monitor the SQL Server instance using non-sysadmin user, create a user with non-sysadmin role and provide the following access to it:

    1. Execute this command to give access to the user:

      GRANT VIEW SERVER STATE TO "login name"
      
    2. Provide database access to the user.

    3. Provide SQLAgentOperatorRole fixed database role in msdb to the user.

  • Preferred credentials are set and validated on all Agents where you want to deploy the plug-in.

  • The OS privileges for the user (set in the Preferred Credentials for the Agent) must meet the requirements documented in the "Setting Credentials for the Job System to Work with Enterprise Manager" section of the Oracle Database Installation Guide for Microsoft Windows available at:

    http://docs.oracle.com/cd/E11882_01/install.112/e24186/postcfg.htm#BABFAEIG
    

    Note:

    If you do not assign the correct privileges for users, the deployment will fail.
  • As part of JDBC URL, either IP Address or host name can be provided. Ensure that the host name can be resolved consistently on the network. Standard TCP tools such as nslookup and traceroute can be used to verify the host name. Validate using the following commands on Management Agent where plug-in is deployed:

    • nslookup <hostname>

      This returns the IP address and fully qualified host name.

    • nslookup <IP>

      This returns the IP address and fully qualified host name.

  • To enable the use of the Backup, Delete Backup, and Restore jobs, the following SQL commands must be processed on the monitored SQL Server database:

    EXEC sp_configure 'show advanced options', 1
    RECONFIGURE 
    EXEC sp_configure 'xp_cmdshell', 1
    RECONFIGURE
    

5 Downloading the Plug-in

You can download plug-ins in online or offline mode. Online mode refers to an environment where you have Internet connectivity, and can download the plug-in directly through Enterprise Manager from My Oracle Support. Offline mode refers to an environment where you do not have Internet connectivity, or where the plug-in is not available from My Oracle Support.

See the Managing Plug-ins chapter in the Oracle Enterprise Manager Cloud Control Administrator's Guide for details on downloading the plug-in in either mode:

http://docs.oracle.com/cd/E24628_01/doc.121/e24473/plugin_mngr.htm#CJGBEAHJ

6 Deploying the Plug-in

You can deploy the plug-in to an Oracle Management Service instance using the Enterprise Manager Cloud Control console, or using the EM Command Line Interface (EMCLI). While the console enables you to deploy one plug-in at a time, the command line interface mode enables you to deploy multiple plug-ins at a time, thus saving plug-in deployment time and downtime, if applicable.

See the Managing Plug-ins chapter in the Oracle Enterprise Manager Cloud Control Administrator's Guide for instructions on deploying the plug-in:

http://docs.oracle.com/cd/E24628_01/doc.121/e24473/plugin_mngr.htm#CJGCDHFG

7 Enabling and Finding TCP/IP Port Information

The following sections provide information you require to enable the TCP/IP port and to find the TCP/IP port for a particular SQL server instance:

7.1 Enabling TCP/IP Port

  1. From the SQL Server Configuration Manager, select your appropriate SQL Server Network Configuration in the left panel and navigate to the SQL Server instance.

    The right panel displays all protocols for the specified SQL Server instance and their status.

  2. Ensure that TCP/IP is enabled.

  3. If TCP/IP is disabled, right-click TCP/IP and select Properties. The TCP/IP Properties dialog box appears.

  4. In the Protocol tab, select enabled, and click Apply.

  5. Restart the SQL Server instance.

7.2 Finding TCP/IP Port

After enabling the TCP/IP protocol, restart the SQL Server to apply the changes.

From the SQL Server Configuration Manager, select the appropriate SQL Server Network Configuration in the left panel and navigate to the SQL Server instance:

The right panel displays all protocols for the specified SQL Server instance and their status.

In the IP Addresses tab, TCP Dynamic Ports row of IP All will give the TCP/IP port of instance.

8 Modifying the Permissions for Database Authentication

Modify the permissions for database authentication so that you enable SQL authentication or Windows authentication, and set sysadmin role for the database user that you are going to use for discovering the target and running jobs.

On the SQL Server, for the user you are going to use for monitoring and running jobs, set the write permissions by following these steps:

Note:

If you do not have a user for Windows Authentication, then create one. To do so, from the task bar, go to Start, select Settings, and then Control Panel. In the Control Panel, double-click Users and Passwords and click Add in the Users tab.
  1. Log in to the Microsoft SQL Server Management Studio with a predefined user account, or if one was not setup for SQL authentication, use Windows Authentication (Figure 5):

    Figure 5 Log In to Microsoft SQL Server

    Surrounding text describes Figure 5 .
  2. Right-click Logins and select New Login… (Figure 6):

    Figure 6 New Login Menu

    Surrounding text describes Figure 6 .
  3. Select either Windows authentication and select a predefined user, or select SQL Server authentication to specify a new user (Figure 7):

    Figure 7 Select User

    Surrounding text describes Figure 7 .
  4. Under the Server Roles page, click the check box for the sysadmin server role (Figure 8):

    Figure 8 Select sysadmin Server Role

    Surrounding text describes Figure 8 .
  5. Click OK.

9 Enabling SQL Authentication or Mixed Authentication

  1. Log in to the Microsoft SQL Server Management Studio with a predefined user account, or if one was not set up for SQL authentication, use Windows Authentication.

  2. Right-click the server you wish to modify and then click Properties.

  3. Select the Security Page.

  4. Under the Server authentication heading choose either the desired authentication: Windows Authentication or SQL Server and Windows Authentication mode.

  5. Click OK.

  6. At this point the SQL server must be restarted. To do so, right-click the server you have just modified and select Restart.

  7. If SQL Server Agent is running, it must also be restarted.

10 Discovering Targets

After successfully deploying the plug-in, follow these steps to add the plug-in target to Cloud Control for central monitoring and management:

  1. From the Setup menu, select Add Target and then Add Targets Manually as shown in Figure 9:

    Figure 9 Add Targets Manually Menu

    Surrounding text describes Figure 9 .
  2. In the Add Targets Manually page, select Add Targets Declaratively by Specifying Target Monitoring Properties, select Target Type as Microsoft SQL Server, select a Monitoring Agent and click Add Manually.

    In the Add Microsoft SQL Server page (Figure 10), provide the following information for the properties

    • Target Name: Unique target name across all Cloud Control targets, such as MSSQL_Hostname. This is the display name in Cloud Control. It represents this SQL Server target across all user interfaces within Cloud Control.

    • Monitoring Database Host Credentials

      • Target System Username (Needed when SQL Server is at remote location): Valid host user name. Required only for remote Agent monitoring. When using WIA remotely this account must be a Windows Domain account with access to the OMA host and target database. For more information, see Configuring Remote Connections to Monitor Targets. The system username must be fully qualified. For example:

        hostname.domainname.com\Administrator
        
      • Target System Password: Password for the System Username. Required only for remote Agent monitoring.

      • Confirm Target System Password: Confirm the password entered for the System Username.

    • Monitoring Database Credentials

      • Database Username (Required for SQL Authentication): Valid user for the database in sysadmin fixed server role.

      • Database Password (Required for SQL Authentication): Corresponding password for the database user.

      • Confirm Database Password (Required for SQL Authentication): Confirm the password entered for the database user.

      • Database Role (Optional): Role assigned to the database user.

      • Confirm Database Role: Confirm database role entered for database user.

    • Properties

      • Connect Using Windows Integrated Authentication (Yes/No): Select Yes for Windows Integrated Authentication, or select No for SQL Authentication.

      • JDBC Driver: (Optional) Microsoft SQL Server 2005 JDBC driver class name.

        For example,

        com.microsoft.sqlserver.jdbc.SQLServerDriver
        
      • JDBC URL: URL for JDBC. It is recommended that the hostname provided in the JDBC URL should be a fully qualified domain name (FQDN). The default port number for Microsoft SQL Server is 1433. You can specify either IP Address or host name. If you are monitoring a Microsoft SQL Server Cluster, then specify the IP address or host name of the virtual SQL Server of the cluster. For example:

        jdbc:sqlserver://<hostname.domain.com>:<port>
        

      Note:

      Specifying a Named Instance is possible for the URL of the JDBC, however consider the following when building the JDBC URL string:
      • Microsoft recommend method for SQL Server hosts with multiple instances of SQL Server installed is to specify unique port numbers for each instance and only specify hostname:port for each URL string.

      • Optionally, to make use of the Instance Name in the URL use the following supported URL format:

        jdbc:sqlserver://hostname:port;instanceName=nameofinstance
        
      • Building JDBC connection URLs with backslashes "\" or without the port number, is not supported by the Microsoft SQL Server plug-in.

  3. Click Test Connection to make sure the parameters you entered are correct.

Figure 10 Add Microsoft SQL Server

Surrounding text describes Figure 10 .

After you deploy and configure the plug-in to monitor one or more targets in the environment, you can customize the monitoring settings of the plug-in. This alters the collection intervals and threshold settings of the metrics to meet the particular needs of your environment. If you decide to disable one or more metric collections, this could impact the reports that the metric is a part of.

11 Authentication Configuration Scenarios

The examples listed below describe supported configuration details for Microsoft SQL Server. Follow the examples and choose the configuration options best suited for your environment.

Note:

Before proceeding with target discovery, manually verify the authentication mode used by manually logging in to the target SQL Server's management tool or request WIA/SQL Authentication credentials from the SQL Server administrator.

Example 1 Local monitoring with SQL Authentication

EM Agent                                    : MACHINE_1
JDBC URL                                    : jdbc:sqlserver://MACHINE_1:<PORT>
Database Username                           : Database_Username
Password of Database User                   : Database_Password
System Password                             : <BLANK>
System Username                             : <BLANK>
Connect Using WIA (Yes/No)                  : No

Database_Username can manually log in to the SQL Server management tool and be granted Sysadmin or correct SQL Server privileges.

Windows OS user is configured to run the Enterprise Manager Agent service and is granted advanced privileges.

Example 2 Local monitoring with Windows Integrated Authentication (WIA)

EM Agent                                    : MACHINE_1
JDBC URL                                    : jdbc:sqlserver://MACHINE_1:<PORT>
Database Username                           : <BLANK>
Password of Database User                   : <BLANK>
System Password                             : <BLANK>
System Username                             : <BLANK>
Connect Using WIA (Yes/No)                  : Yes

Windows OS User can manually log in to the SQL Server management tool using WIA, is configured to run Enterprise Manager Agent service, is granted advanced privileges, and is granted Sysadmin or correct SQL Server privileges.

Example 3 Remote monitoring with SQL Authentication

EM Agent                                  : MACHINE_1
JDBC URL                                  : jdbc:sqlserver://MACHINE_REMOTE:<PORT>
Database Username                         : Database_Username  
Password of Database User                 : Database_Password
System Username                           : REMOTE_Windows_OS_User
System Password                           : REMOTE_Windows_OS_Password 
Connect Using WIA (Yes/No)                : No

Sysadmin or SQL Server privileges are granted to the Database_Username.

Advanced privileges granted to REMOTE_Windows_OS_User within the SQL Server host machine, and can log in to SQL Server host machine.

Example 4 Remote monitoring with Windows Integrated Authentication (WIA)

EM Agent                                  : MACHINE_1
JDBC URL                                  : jdbc:sqlserver://MACHINE_REMOTE:<PORT>
Database Username                         : <BLANK>
Password of Database User                 : <BLANK>
System Username                           : REMOTE_Windows_OS_User
System Password                           : REMOTE_Windows_OS_Password
Connect Using WIA (Yes/No)                : Yes

REMOTE_Windows_OS_User can log in to SQL Server host machine, can manually login to the SQL Server management tool using WIA, granted advanced privileges, granted Sysadmin or correct SQL Server privileges, and must be a Windows Domain account with access to OMA host and target database.

Example 5 Cluster remote monitoring with SQL Authentication

Cluster  = SQLServer_Cluster_Hostname
Nodes    = Node1_Hostname
           Node2_Hostname
           etc..

EM Agent                      : ANY MACHINE
JDBC URL                      : jdbc:sqlserver://SQLServer_Cluster_Hostname:<PORT>
Database Username             : Database_Username  
Password of Database User     : Database_Password
System Username               : REMOTE_Windows_OS_User
System Password              : REMOTE_Windows_OS_Password
Connect Using WIA (Yes/No)   : No

Sysadmin or SQL Server privileges are granted to the Database_Username.

REMOTE_Windows_OS_User granted advanced privileges within the SQL Server nodes and can log in to SQL Server cluster hostname. Test the login by using Windows Remote Desktop.

SQLServer_Cluster_Hostname is virtual hostname or IP of the SQL Server Clustered Service and not the Windows Cluster Hostname.

Example 6 Cluster remote monitoring with Windows Integrated Authentication

Cluster  = SQLServer_Cluster_Hostname
Nodes    = Node1_Hostname
           Node2_Hostname
           etc..

EM Agent                      : ANY MACHINE
JDBC URL                      : jdbc:sqlserver://SQLServer_Cluster_Hostname:<PORT>
Database Username             : <BLANK>
Password of Database User     : <BLANK>
System Username               : REMOTE_Windows_OS_User
System Password               : REMOTE_Windows_OS_Password
Connect Using WIA (Yes/No)    : Yes

REMOTE_Windows_OS_User can log in to SQL Server cluster hostname, can manually login to the SQL Server management tool using WIA, granted advanced privileges, granted Sysadmin or correct SQL Server privileges, and must be a Windows Domain account with access to OMA host and target database.

SQLServer_Cluster_Hostname is virtual hostname or IP of the SQL Server Clustered Service and not the Windows Cluster Hostname.

Note:

Where a User account requires Advanced Privileges, this includes the following Operation System rights:
  • Act as part of the operating system.

  • Adjust memory quotas for a process.

  • Log on as batch job.

  • Replace a process-level token.

12 Verifying and Validating the Plug-in

After waiting a few minutes for the plug-in to start collecting data, use the following steps to verify and validate that Enterprise Manager is properly monitoring the plug-in target:

  1. Click the Microsoft SQL Server target link from the All Targets page. The Microsoft SQL Server home page appears as shown in Figure 11:

    Figure 11 Microsoft SQL Server Home Page

    Surrounding text describes Figure 11 .
  2. Verify that no metric collection errors are reported by clicking Monitoring and then Metric Collection Errors from the Target menu.

  3. Ensure that reports can be seen and no errors are reported by clicking Information Publisher Reports in the Target menu and viewing reports for the Microsoft SQL Server target type.

  4. Ensure that configuration data can be seen by clicking Configuration and then Last Collected in the Target menu. If configuration data does not immediately appear, click Refresh in the Latest Configuration page.

  5. View the Database Page by selecting the Microsoft SQL Server drop down under the target name and selecting Database. The database page appears (Figure 12). The database page contains database specific performance and configuration metrics as well as backup and restore functionality. The database will be selected from a drop­down menu.

    Figure 12 Microsoft SQL Server Database Page

    Surrounding text describes Figure 12 .
  6. View the Performance Page by selecting the Microsoft SQL Server drop down under the target name and selecting Performance. The Performance page appears (Figure 13). The performance page contains convenient performance graphs built from collected metrics.

    Figure 13 Microsoft SQL Server Performance Page

    Surrounding text describes Figure 13 .
  7. View the Analysis Page by selecting the Microsoft SQL Server drop down under the target name and selecting Analysis. The Analysis page appears (Figure 14). The analysis page displayed SQL query and session information, as well as the "Kill Session" job button to quickly end any problematic sessions.

    Figure 14 Microsoft SQL Server Analysis Page

    Surrounding text describes Figure 14 .

13 Configuring Connections

This section provides details about configuring connections for monitoring targets and executing jobs and includes the following topics:

13.1 Configuring Remote Connections to Monitor Targets

If you want to monitor targets using remote Agents, then Oracle recommends that you do the following security configurations on every system where SQL Server target resides.

  • Set WMI namespace security.

  • Restrict access to the registry from a remote computer.

  • Set DCOM Security to allow user to access remotely.

  • Set privileges for System User to access Windows performance counters remotely as follows:

    1. Locally on the Microsoft Windows node hosting the Agent, open the Local Security Settings Windows Tool. Go to Start, select Control Panel, and then select Administrative Tools, select Computer Management, select System Tools, then Local Users and Groups, and select Groups.)

    2. Add System Username to Performance Monitor Group as shown in Figure 15:

      Figure 15 Performance Group

      Surrounding text describes Figure 15 .
  • Set access privileges of SQL Server Services to allow user to access a computer remotely.

  • Set privileges for System User of target on Oracle Management Agent for Windows Integrated Authentication based monitoring.

    1. Locally on the Microsoft Windows node hosting the Agent, open the Local Security Settings Windows Tool. Go to Start, select Control Panel, and then select Administrative Tools, and select Local Security Policy.

    2. Click on Local Policies and then User Rights Assignment.

    3. Assign the following right to the System User of the target:

      Logon as batch job

  • Configure Allow Remote Administration Exception in Windows Firewall if Windows firewall is enabled on the SQL Server target system.

13.2 Configuring Connections to Execute Jobs

If you want to execute jobs using local or remote Agents, then Oracle recommends that you do the following security configurations on every system where SQL Server target resides.

  • Set WMI namespace security.

  • Set DCOM Security to allow user to access a computer remotely.

For configuration details, refer to the following:

14 Creating and Editing Jobs

To create and edit jobs, follow these steps:

  1. In Enterprise Manager Cloud Control 12c, click Enterprise, then Job, then click Activity.

  2. On the Job Activity page (Figure 16), select a job type from the Create Job menu and click Go.

    Select one of the following:

    • Microsoft SQL Server and/or SQL Agent Start

    • Microsoft SQL Server and/or SQL Agent Stop

    • Microsoft SQL Server Pause or Resume

    • Microsoft SQL Server Kill Session

    • Microsoft SQL Server Backup Database

    • Microsoft SQL Server Delete Backup Database

    • Microsoft SQL Server Restore Database

    Figure 16 Microsoft SQL Server Job Activity Page

    Surrounding text describes Figure 16 .
  3. In the General tab of the Create <Job Type> Job page, provide a name for the job and add the individual targets or one composite target such as a Group.

    Note:

    If you are editing a job, then modify the job name and the selected targets.
  4. In the Parameters tab of the Create <Job Type> Job page, from the Options menu, select an appropriate option to make the job function accordingly when it starts.

    You can select one of these options as shown in Table 1:

    Table 1 Job Parameters Options

    Job Type Available Options

    Microsoft SQL Server and/or SQL Agent Start

    • Start SQL Server and SQL Server Agent services

      (You will select this option when both, SQL Server and SQL Server Agent, are stopped or when SQL Server is running but the SQL Server Agent is stopped)

    • Start SQL Server service

      (You will select this option when both, SQL Server and SQL Server Agent, are stopped and if you want to start only the SQL Sever)

    Microsoft SQL Server and/or SQL Agent Stop

    • Stop SQL Server and SQL Server Agent services.

      You will select this option:

      • When both SQL Server and SQL Server Agent are running.

      • When SQL Server is paused but the SQL Server Agent is running.

      • When SQL Server is running/paused but the SQL Server Agent is stopped.

    • Stop SQL Server Agent service.

      (You will select this option when you want to stop a running SQL Server Agent)

    Microsoft SQL Server Pause or Resume

    • Pause SQL Server service

      (You will select this option when you want to pause a running SQL Server)

    • Resume SQL Server service

      (You will select this option when you want to resume a paused SQL Server)

    Microsoft SQL Server Kill Session

    • End a single active SQL Server user session.

      (You will select this option to end an active user session by specifying the session id)

    Microsoft SQL Server Backup Database

    • Creates a backup of the database specified by Database Name in the Parameters section of the job.

    • Unless specified by editing the monitoring configuration of a deployed target in the Backup Path value, the database backup files will be saved to the default SQL Server backup location. The path specified must not end in a backslash.

    • The Backup job is also available as a button on the Database page in the Backup Management section as Backup Now.

      (You will select this job when you want to take a backup of the specified database)

    Microsoft SQL Server Delete Backup Database

    • Removes the backup file from the SQL Server by specifying Media Set ID and full path to the backup file in the Job Parameters section.

    • The Delete Backup job is also available as a button on the Database page in the Backup Management section as Delete.

      (You will select this job when you want to remove backup file that is no longer needed)

    Microsoft SQL Server Restore Database

    • Restores a database from backup by specifying the full path to the backup file as well as the database name in the Job Parameters section.

    • The Restore Database jobs is also available as a button on the Database page in the Backup Management section as Restore.

      (You will select this option when you want to restore a database from a backup taken using the Microsoft SQL Server Backup Database job)


    Cloud Control starts the SQL server and agent services according to the selection made.

  5. In the Credentials tab of the Create <Job Type> Job page, select an appropriate option for credentials.

    You can choose to use the preferred credentials that are already set or override the preferred credentials with new credentials. In either case, you need to provide the credentials for agent host and database host.

    To set the preferred credentials, click Preferences at the top-right corner of the Cloud Control console. From the left-vertical navigation bar, click Preferred Credentials. Cloud Control displays the Preferred Credentials page. On this page, you can set the preferred credentials

  6. In the Schedule tab of the Create <Job Type> Job page, schedule the job.

  7. In the Access tab of the Create <Job Type> Job page, define or modify the access you want other users to have to this job.

  8. Click Submit to create the job.

Notes:

  • To enable use of the Job buttons found in the Summary section of the Target home page and the Backup Management buttons found in the Database page, be sure to set the Preferred Credentials with SQL Server Authentication for the Microsoft SQL Server target type.

  • Regardless of the authentication used for monitoring, the Kill Session, Backup, Delete Backup, and Restore jobs require SQL Server Authentication. To use these jobs be sure to specify credentials for SQL Server authentication.

  • The Microsoft SQL Server Pause or Resume job is only supported for stand-alone Microsoft SQL Server instances. Pause of Resume Jobs submitted for Microsoft SQL Server 2005, 2008, 2012, and 2014 cluster instances will fail with the appropriate error message.

15 Using the Backup and Restore Jobs

  1. From the Targets, select All Targets, then select the Microsoft SQL Server target.

  2. From the Microsoft SQL Server menu, select Database as shown in Figure 17:

    Figure 17 Select Database

    Surrounding text describes Figure 17 .
  3. Use the drop down to select the database you wish to back up as shown in Figure 18.

    Figure 18 Select a Database

    Surrounding text describes Figure 18 .

    Several options are available using the Backup Management Region.

  4. Click Backup Now to create a backup immediately (Figure 19). Click Yes on the popup to confirm.

    Figure 19 Backup Now

    Surrounding text describes Figure 19 .

    When the backup is complete, it will appear in the list (Figure 20):

    Figure 20 Completed Backup

    Surrounding text describes Figure 20 .
  5. If you wish to give your backup a custom name, use the text box before clicking the Backup Now button.

  6. You can also create a backup schedule by clicking Schedule Backup.

  7. Click Yes to confirm that you would like to go to Enterprise Manager's job creation system where you can complete the scheduling process.

  8. Give the Job a name (Figure 21):

    Figure 21 Job Name

    Surrounding text describes Figure 21 .
  9. Click on Parameters and specify the name of the database you wish to backup.

  10. Optionally, you can specify a custom backup name.

  11. Select or enter credentials as shown in Figure 22. If you've configured Preferred Credentials for the target, you can select SYSADMIN Database Credentials, Target System Credentials, and Agent Host Credentials.

    Figure 22 Enter Credentials

    Surrounding text describes Figure 22 .
  12. Use Enterprise Manager's built-in scheduling options to define the time and recurrence of the schedule as shown in Figure 23:

    Figure 23 Scheduling Options

    Surrounding text describes Figure 23 .
  13. Click Submit. The schedule will be shown in the Job Activity view (Figure 24).

    Figure 24 Job Activity View

    Surrounding text describes Figure 24 .

Note:

You can only restore backups that meet the following criteria. The backup is:
  • File backup (not tape)

  • Whole database (not differential)

  • MS SQL Server knows this backup (backup is in the list of known backups, list comes from query, seen below)

  • Not password protected

  • Of the type 'SIMPLE'

  • Not damaged

16 Using the Microsoft SQL Server Plug-in Reports

To further aid administrators with critical tasks such as problem diagnosis, trend analysis and capacity planning, the Microsoft SQL Server plug-in includes eighteen out-of-box reports:

Figure 25 Microsoft SQL Server Reports

Surrounding text describes Figure 25 .

To generate a new report from one of the out-of-the-box reports provided by Oracle, follow these steps:

  1. From the Enterprise menu, select Reports, then Information Publisher Reports as shown in Figure 26:

    Figure 26 Reports Menu

    Surrounding text describes Figure 26 .
  2. Choose Microsoft SQL Server from the Target Type list inside the Search menu and then click Go as shown in Figure 27:

    Figure 27 Search Reports

    Surrounding text describes Figure 27 .
  3. After the reports have been sorted to Microsoft SQL Server reports only, find the desired report and click on the report title hyperlink.

  4. In the Specify Target for Report page, click the magnify glass magnifying glass icon to find the specific Microsoft SQL Server target you wish to create a report for.

  5. After selecting the target, click Continue to finish generating the report.

Table 2 shows the Information Publisher Reports provided by Oracle:

Table 2 Microsoft SQL Server Plug-in Reports

Report Name Report Description

Microsoft SQL Server Database Configuration

Displays Configuration Information for the various Databases.

Microsoft SQL Server System Configuration

Displays Configuration Information for the SQL Server System.

License Pack Usage (Target)

Displays the License Pack Usage for a target.

Membership (Target)

Displays the list of aggregate targets where the specified target is a member.

20 Most Common Alerts (Target)

Displays 20 most common alerts for a target over the last 24 hours.

Alerts History (Target)

Displays alerts for a target over the last 24 hours.

Outstanding Alerts (Target)

Displays outstanding alerts for a target.

Availability History (System)

Displays availability history for a system over the last 24 hours.

Availability History (Target)

Displays availability history for a target over the last 24 hours.

Microsoft SQL Server Database Backups and Jobs

Displays Information about the Database Backups and Jobs.

Microsoft SQLServer Memory Statistics

Displays Information about the Memory in SQL Server.

Microsoft SQLServer Performance

Displays Information about the Performance of the SQL Server.

Microsoft SQL Server Query and Session Performance

Displaying Information about the Performance of the Most Active Queries and Sessions of the SQL Server.

Microsoft SQL Server Statistics

Displays Statistical Information for SQL Server.

Microsoft SQL Server Cluster

Displays Information about the SQL Server Cluster.

Target Status Diagnostics Report: Agent-based targets

This report summarizes status and availability transitions for agent-based targets and the monitoring agent(s).

Target Status Diagnostics Report: Repository-based targets

This report summarizes status and availability transitions for repository-based targets.

Microsoft SQL Server Space Usage

Displays Information about Space Usage in the Database.


17 Upgrading the Plug-in

The Self Update feature allows you to expand Enterprise Manager's capabilities by updating Enterprise Manager components whenever new or updated features become available. Updated plug-ins are made available via the Enterprise Manager Store, an external site that is periodically checked by Enterprise Manager Cloud Control to obtain information about updates ready for download. See the Updating Cloud Control chapter in the Oracle Enterprise Manager Cloud Control Administrator's Guide for steps to update the plug-in:

http://docs.oracle.com/cd/E24628_01/doc.121/e24473/self_update.htm

18 Undeploying the Plug-in

See the Managing Plug-ins chapter in the Oracle Enterprise Manager Cloud Control Administrator's Guide for steps to undeploy the plug-in:

http://docs.oracle.com/cd/E24628_01/doc.121/e24473/plugin_mngr.htm#CJGEFADI

19 Troubleshooting the Plug-in

For information about the troubleshooting scenarios that you might encounter while working with the System Monitoring plug-ins, see the Oracle Enterprise Manager System Monitoring Plug-in Troubleshooting Guide for Third-Party Database Plug-ins:

http://docs.oracle.com/cd/E24628_01/em.121/e35212/toc.htm

20 Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.


System Monitoring Plug-in Installation Guide for Microsoft SQL Server, Release 12.1.0.5.0

E35211-10

Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.