ADO.NET Performance Profiling Tools

.NET

For developers and operations teams building and managing applications with ADO.NET for SQL, MySQL, and Oracle, the AppDynamics platform provides a comprehensive solution for monitoring and managing the performance of your .NET applications. With rapid installation and the most scalable architecture in the industry, AppDynamics solutions help you deploy your applications more quickly and with more confidence.

SQL Application flow map

In this example, AppDynamics auto-discovers two ASP.NET tiers and two backends. The NWTraders-WebLog and NWTraders-Portal tiers are ASP.NET. NWTrader-Portal is making a Microsoft SQL Server ADO.NET backend database call. The flowmap shows the communication as the average number of calls per minute the tier is making for a ADO.NET call and the average response time for a single call.

Transaction snapshots

AppDynamics takes transaction snapshots which contain diagnostic data to help you quickly analyze and troubleshoot problems with Microsoft SQL Server ADO.NET backend and other types of business transactions.In this example, it displays transaction snapshots for /products.aspx business transaction.

Call graph

Drill down into a transaction snapshot to display the call graph for Microsoft SQL Server ADO.NET backend transactions. The call graph displays the code execution sequence timing, so you can identify which method has problems. In this example, The System.Web.UI.Control:OnLoad method is taking 20 ms, 6.7% of the time for the Microsoft SQL Server ADO.NET backend call.

Backend dashboard

Microsoft SQL Server ADO.NET backend calls are detected under Databases. This section describes about the type of call, calls/min, response time etc. In this example, there is a Microsoft SQL Server ADO.NET backend call with 1142 calls/min, 19ms response time and 34,269 calls.

Microsoft SQL Server ADO.NET backend performance

AppDynamics collects metrics for backend performance (Microsoft SQL Server ADO.NET in this case). Use the metric browser to create graphs of critical statistics. The graph below shows calls per minute (in green), average response time (in blue). In this example, the average response time was maximum at 1:37am.

MySQL: Application flow map

In this example, AppDynamics auto-discovers an ASP.NET tier and six backends. The ABCorpApp-Portal is making four ADO.NET backend database calls.The flow map shows the communication as the average number of calls per minute the tier is making for four ADO.NET calls and the average response.

Transaction snapshots

AppDynamics takes transaction snapshots which contain diagnostic data to help you quickly analyze and troubleshoot problems with MySQL ADO.NET backend and other types of business transactions

Call Graph

Drill down into a transaction snapshot to display the call graph for MySQL ADO.NET backend transactions. The call graph displays the code execution sequence timing, so you can identify which methods has problems. In this example, TheMySql.Data.MySQLCleint.MySqlCommand. ExecuteReader method is taking 140 ms, 4.8% of the time for the MySQL ADO.NET backend call, it is displayed in red as an error had occured while executing this method.

Database dashboard

MySQL ADO.NET backend calls are detected under Databases. This section describes about the type of call, calls/min, response time etc. In this example, there is a MySQL ADO.Net backend call with 105 calls/min, 214ms response time and 526 calls.

Oracle ODP.NET ADO.NET backend performance

AppDynamics collects metrics for backend performance (Oracle ODP.NET ADO.NET in this case). Use the metric browser to create graphs of critical statistics. The graph below shows calls per minute (in green) and average response time (in blue).

MySQL ADO.NET backend performance

AppDynamics collects metrics for backend performance (MySQL ADO.NET in this case). Use the metric browser to create graphs of critical statistics. The graph below shows calls per minute (in green), average response time (in blue) and errors per min (in red). In this example the average response time was maximum at 10:46pm, calls/min was minimum at 11:01pm and errors/min was minimum at 11:01pm and 11:06pm.

Oracle: Application flow map

In this example, AppDynamics auto-discovers an ASP.NET tier and 2 backends. Home tier is making 2 ADO.NET backend database calls. The flowmap shows the communication as the average number of calls per minute the tier is making for 2 ADO.NET calls and the average response.

Transaction snapshots

AppDynamics takes transaction snapshots which contain diagnostic data to help you quickly analyze and troubleshoot problems with Oracle ODP.Net ADO.NET backend and other types of business transactions.

Call Graph

Drill down into a transaction snapshot to display the call graph for Oracle ODP.NET ADO.NET backend transactions. The call graph displays the code execution sequence timing, so you can identify which methods has problems. In this example, The Oracle.DataAccess.Client.OracleConnection:Open method is taking 63686 ms, 99.9% of the time for the Oracle ODP.Net ADO.NET backend call, it is displayed in red as an error had occured while executing this method.Click on the SQL Calls tab in the call graph. This shows the query executed, type of query, no. of times the query executed, avg time it takes to execute etc.

Databases dashboard

Oracle ODP.NET ADO.NET backend calls are detected under Databases. This section describes about the type of call, calls/min, response time etc. In this example, there is a Oracle ODP.NET ADO.NET backend call with 28046 calls/min, 1ms response time. Double click on the Oracle ODP.NET ADO.NET backend call will open its dashboard. This dashboard shows the flow map of the Oracle ODP.NET ADO.NET backend call.

Oracle ODP.NET ADO.NET backend performance

AppDynamics collects metrics for backend performance (Oracle ODP.NET ADO.NET in this case). Use the metric browser to create graphs of critical statistics. The graph below shows calls per minute (in green) and average response time (in blue).

Start a 15 day free trial now