SQLServer Monitor

SQLServer Monitor complements Agileload by extending the range of data collection and monitoring options available, by adding the ability to monitor and record performance data from SQLServer components of target systems. It enables the creation of Collectors that can include a number of monitoring and data collection options. Results data generated by SQLServer Monitor Collectors can be displayed and analyzed to help to identify bottlenecks that occur on target SQLServer Systems during Job-runs.

Prerequisite:

  1. A Windows account that can retrieve performance counters and registry information from the server on which Windows is running. This account must have access to the server's performance monitor counters, and read access to the server's Windows registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib path).
    (eg: To view performance counters, a user must be a member of the local "Performance Monitor Users" group, "Performance Log Users" group, "Administrators" group, or equivalent)
    (eg: A user in the "Administrators" group may not be able to view performance counters. Use an account that is member of the "Performance Monitor Users" group)
    Windows XP and Windows 2000: The Administrator or users in the "Administrator" group can view performance counters without restriction.

  2. Open the "Settings\Control Panel\Administrative Tools\Local Security Policies" ("Settings\Control Panel\Administrative Tools\Domain Security Policies"), select the "\Local Policies\Security Options" option in the tree view:



     
  3. On the target machine, grant local "Performance Monitor Users" and "Performance Log Users" groups ("Administrators" group for Windows 2000 and Windows XP) read permission on "SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib" registry path. (restart "Remote registry" service)
  4. The "Remote Registry" and "Net Logon" services must be started on the monitored windows system.
     

  5. If a firewall is running on the monitored windows system, TCP ports 139 and 445 must be opened (eg: SMB protocol).

    Under "Windows Server 2008", if the windows firewall is activated, open the "Settings\Control Panel\Administrative Tools\Server Manager", select the "Configuration\Windows Firewall with Advanced Security\Inbound Tules" entry in the tree view and activate the "File and Printer Sharing (SMB-In)" option.

  6. On the AgileLoad Machine, a dedicated windows session must be created. The session parameters can be specified in the AgileLoad Daemon configuration window. If the session parameters are not already set in the AgileLoad Daemon, the LogonSessionCfg tool is automatically launched:

    Specify a login in the Login field, its associated password in the Password field, a domain in the Domain field and click "OK".





Go back to the Learning center:


Copyright © AgileLoad. All rights reserved.
Agile Load testing tool| Contact AgileLoad | Terms of Use | Sitemap