All
0 Results filtered by:
We couldn't find any results
You can search all listings, or try a different spelling or keyword. Still nothing? Dynatrace makes it easy to create custom apps.
Microsoft SQL Server (local)Microsoft SQL Server (local)
Improve the health and performance monitoring of your Microsoft SQL Servers.
Extension- Product information
- Release notes
Overview
Microsoft SQL Server database monitoring is based on a local monitoring approach implemented as a Dynatrace OneAgent extension. The extension uses WMI queries to collect key performance and health metrics from the SQL Server instance running on the host, extending your visibility.
Use cases
- Understand the resource impact that your applications have on your database.
- Understand the impact of resource shortages, locks or other database issues have on your application by observing the database server itself.
- Track health and performance of the MS SQL servers.
- Speed up the application problem diagnosis, where it’s caused by the database.
Get started
Activation
- Make sure OneAgent is installed and running on the SQL Server host.
- Make sure that log monitoring is enabled to be able to troubleshoot the monitoring.
- Activate the extension from the Hub.
Compatibility information
Supported versions of SQL Server:
Any version of SQL Server with active extended support by Microsoft is supported by this extension. Please refer to the official Microsoft documentation about lifecycle dates for SQL Server.
Supported types of SQL Server:
- SQL Server on Windows (editions: Enterprise, Standard, Developer)
Warnings:
- If you have several instances on the same host, this extension could cause additional CPU utilization. For now, please use the Remote SQL Server extension in such scenarios.
- Versions 1.1+ of the extension and later are incompatible with the verson 1.0 or the ones released earlier.
Extension content
Content typeNumber of items included
screen injections
1
screen properties
1
generic relationship
1
dashboards
1
screen actions
2
screen chart groups
6
screen layout
1
metric metadata
18
list screen layout
1
generic type
1
screen entities lists
3
Feature sets
Below is a complete list of the feature sets provided in this version. To ensure a good fit for your needs, individual feature sets can be activated and deactivated by your administrator during configuration.
Feature setsNumber of metrics included
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Processes blocked | sql-server.local.general.processesBlocked | Number of currently blocked processes | Count |
| Transactions | sql-server.local.general.transactions | Number of transaction enlistments (local, dtc, and bound) | Count |
| User connections | sql-server.local.general.userConnections | Number of users currently connected to SQL Server | Count |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Connection memory | sql-server.local.memory.connection | Total amount of dynamic memory the server is using for maintaining connections | KiloByte |
| Memory grants outstanding | sql-server.local.memory.grantsOutstanding | Number of processes that have successfully acquired a workspace memory grant | Count |
| Memory grants pending | sql-server.local.memory.grantsPending | Number of processes waiting for a workspace memory grant | Count |
| Target server memory | sql-server.local.memory.target | Amount of memory that can be consumed by memory manager | KiloByte |
| Total server memory | sql-server.local.memory.total | Amount of memory the server has committed using the memory manager | KiloByte |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Page splits | sql-server.local.accessMethods.pageSplits.count | Number of page splits that occur as a result of overflowing index pages | PerSecond |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Buffer cache hit | sql-server.local.buffers.cacheHitRatio | Percentage of pages found in the buffer cache without having to read from disk | Percent |
| Checkpoint pages | sql-server.local.buffers.checkpointPages.count | Number of pages flushed to disk by a checkpoint or other operations that require all dirty pages to be flushed | Count |
| Page life expectancy | sql-server.local.buffers.pageLifeExpectancy | Number of seconds a page will stay in the buffer pool without references | Second |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Latch waits | sql-server.local.latches.waits.count | Number of latch requests that could not be granted immediately | Count |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Batch requests | sql-server.local.sql.batchRequests.count | Number of Transact-SQL command batches received | Count |
| SQL compilations | sql-server.local.sql.compilations.count | Number of SQL statement compilations | Count |
| SQL re-compilations | sql-server.local.sql.recompilations.count | Number of SQL statement re-compilations | Count |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Lock waits | sql-server.local.locks.waits.count | Number of lock requests that required the caller to wait | Count |
| Deadlocks | sql-server.local.locks.deadlocks.count | Number of lock requests that resulted in a deadlock | Count |
Customer story Photobox
“With such a diverse technology stack, not many solutions were able to meet all our needs, but Dynatrace was the exception.”
Alex Hibbitt
Engineering Director, SRE & Fulfillment
Related to Microsoft SQL Server (local)
Full version history
To have more information on how to install the downloaded package, please follow the instructions on this page.
ReleaseDate
Full version history
Improvements:
- Host name for each SQL Server instance entity is now properly resolved. Instead of
SQL Server (HOST-9A55C8D98F33TOD)the entity name is resolved to true host name:SQL Server (my-host)
Full version history
Bug fixes:
- Instance entities now have unique names, based on the underlying HOST ID.
Example:
SQL Server (HOST-9A55C8D98F33TOD). Previously all entities had the same user facing nameSQL Server Local (localhost). - Fix for validation errors that involve metrics with
:smooth(skipfirst)in their name. - Fix for
err:Exception occurred. (Invalid class): see below for added support for named instances.
Improvements:
- Link to parent host is added on Instance screen.
- Link to parent host is added on properties card of the Instance under the "Host" attribute.
- Local address of the detected connection is added on properties card under the "Device" attribute.
Instancedimension removed from all metrics, because it was never reported.- Dashboard was redisigned to better fit on smaller screens.
Features:
- Link to the detected SQL Server instance entity is added on Host screen under the "SQL Server Local Instances".
- Support for named instances has been added.
Warning:
- Extension is only proven to work with a single SQL Server instance (named or default) installed on host.
Full version history
- Fixed issue with
Fault retrieving dimension for key:instance err:Unknown nameerror. - Added compatibility with remote SQL Server extension.
- All metrics had their prefix changed from
sql-server.tosql-server.local.to distinguish collected metrics from those reported by remote SQL Server extension.
Full version history
Reimplementation of EF1 local WMI monitoring extension using EF2.