AimBetter supports monitoring database calls executed by supported .NET applications hosted on IIS.
Database call monitoring provides visibility into database activity within the web request execution flow, allowing users to identify how much time is spent executing database calls as part of a monitored request.
Supported Databases and Providers
The following database providers are supported:
| Database | Supported drivers/providers | Name displayed in UI |
|---|---|---|
| SQL Server | System.Data.SqlClientMicrosoft.Data.SqlClient | MSSQL |
| Oracle | Oracle.ManagedDataAccess (ODP.NET Managed)Oracle.DataAccess (ODP.NET Unmanaged) | Oracle |
| MySQL | MySql.Data (Connector/NET)MySqlConnector | MySQL |
| PostgreSQL | Npgsql | PostgreSQL |
Requirements
For database calls to be monitored and associated with web requests, the following conditions must be met:
- The application must be a supported .NET application hosted on IIS.
- Database calls must be executed within the monitored IIS application.
- The application must use one of the supported database drivers/providers listed above.
When these requirements are met, AimBetter associates database calls with their corresponding monitored web requests, providing visibility into database execution time within the request flow.
Scope and Limitations
Database call monitoring is limited to calls executed within the monitored IIS application process.
In some systems, such as Priority, database access may be handled by a separate application process or service outside IIS.
In these cases:
- Web request monitoring remains available.
- Database calls executed outside the monitored IIS process are not captured as part of the request flow.
- Database execution time may therefore not appear in the web request details.
Important: This limitation applies only to associating database calls with web requests. It does not affect the availability of AimBetter’s independent database monitoring capabilities. A database can be fully supported for database monitoring even if its calls cannot be traced within the IIS request flow.