Datasheet : Monitor SQL Server Performance with SQL Diagnostic Manager for SQL Server

The monitoring of SQL Server environments is much more straightforward with quality monitoring applications. The proper monitoring applications can let database administrators know when something may be going wrong. SQL Diagnostic Manager for SQL Server is a monitor and advisor tool for SQL Server. It provides database administrators and system administrators with the right metrics to manage and optimize applications during development and production. It provides the tools to manage many SQL Server servers, to tune the database infrastructure, and to aid in finding and fixing problems with database applications before they develop into more serious issues or costly outages.

Monitor instances

  1. View the status, performance, and essential configuration settings of all of the monitored instances and all of the active alerts in the desktop, web, and mobile web console.
  2. Monitor groups of instances and all groups, including monitors to view several important specifics, see an overview, and drill down to detailed metrics.
  3. Get an overview of a specific instance and its activities to diagnose inter-related issues, using quick links to display the associated details and review recommended solutions.

Monitor vital metrics

  1. Monitor sessions to diagnose performance bottlenecks caused by blocking or locked sessions, trace sessions to find the root cause, and kill sessions to improve performance.
  2. Monitor query performance to log and analyze queries, set up criteria for the query capture, and filter the results to analyze the returned queries.
  3. Monitor system resources on the server hosting the instance and the resources SQL Server uses to improve application design and remove resource contention.
  4. Monitor databases, including backups, restores, table sizes and structures, table row counts, index disk space, configurable options, and replication status.
  5. Manage services including SQL Server Agent, SQL Server Browser, Full-Text Search, Distributed Transaction Coordinator, and Replication.
  6. View, filter, and search current and archived logs related to SQL Server to diagnose problems where a history of events is necessary to form context.

Analyze instances

  1. Run a prescriptive analysis on instances to find and resolve performance problems by scanning for potential problems.
  2. Target the most common areas of performance problems such as queries, server configuration, security, database objects, and memory.
  3. View a useful set of recommendations for improving performance.

Alert on SQL Server metrics

  1. Configure alerts to inform and warn about approaching issues with the instances.
  2. Respond to alerts by sending notifications and automatically performing actions when reaching an alert threshold.
  3. Do not alert for repeated occurrences while addressing the problem. Only alert again if the situation recurs after correcting the condition triggering the alert.
  4. Select from many alerts to monitor and warn about the instances and availability groups.
  5. Configure the alerts to receive alerts only on the metrics that fall outside of the typical performance of the environment.
  6. The metric alerts cover backups, databases, database-as-a-service, logs, operations, queries, resources, services, sessions, and virtualization.

Manage alerts

  1. Configure general alert settings as templates to apply to servers and groups of servers in the environment.
  2. Set the thresholds for alerts, add comments to alert, and customize the informational, warning, and critical levels for sending alert notifications.
  3. Adjust the filters to organize alerts and to selectively view relevant alerts.

Report on performance

  1. Create reports to analyze current and historical performance and statistical data, and deploy reports to Microsoft Reporting Server.
  2. Access pre-defined reports for monitoring (for server, virtualization, and activity), analysis (for server, database, and resource), and planning (for disk, database, and table).
  3. Create, import, and export custom reports with specific page layouts and filters to select the information to include in the reports.

Use built-in, real-time communication feed

  1. Collaborate, share knowledge and expertise, and stay updated on the most recent and critical issues using real-time feeds from the desktop console and the mobile web console.
  2. Follow application alerts, server activity, and comments by coworkers. Give status updates as the team manages and resolves any issues.
  3. Interact with an instance by viewing the server profile, posting to the server's wall, and following the server.

Manage SQL Diagnostic Manager

  1. Use application security to appoint access to servers and databases that individual users and groups of users have within SQL Diagnostic Manager.
  2. Use the changelog to review changes in the configuration of SQL Diagnostic Manager and to view critical actions (such as adding servers for monitoring).
  3. Use the centralized import and export wizard to share alert templates, alert responses, custom reports, and custom counters.

Integrate with other systems

  1. Integrate SQL Diagnostic Manager with Microsoft System Center Operations Manager (SCOM) to extend SCOM's capabilities to monitor SQL Server.
  2. Use Microsoft PowerShell to automate SQL Diagnostic Manager functions such as making bulk configuration changes and executing automatic alert actions.
  3. Launch SQL Workload Analysis in the context of the monitored instance to view a granular breakdown of the wait states and easily drill down to isolate problems.

Download This Datasheet Start a FREE Trial

Share This
Contact IDERA:
+1 (713) 523-4433