{"id":6044,"date":"2013-10-07T11:38:51","date_gmt":"2013-10-07T11:38:51","guid":{"rendered":"https:\/\/test.simple-talk.com\/uncategorized\/new-database-profiling-support-in-ants-performance-profiler\/"},"modified":"2016-07-28T10:53:56","modified_gmt":"2016-07-28T10:53:56","slug":"new-database-profiling-support-in-ants-performance-profiler","status":"publish","type":"post","link":"https:\/\/www.red-gate.com\/simple-talk\/blogs\/new-database-profiling-support-in-ants-performance-profiler\/","title":{"rendered":"New database profiling support in ANTS Performance Profiler"},"content":{"rendered":"

In May last year, the ANTS Performance Profiler<\/a> team added the ability to profile database requests<\/a> your application makes to SQL Server or Oracle. The really cool thing is that you’re shown those requests in the application’s call tree, so you can see what .NET code caused those queries to run. It’s particularly helpful if you’re using an ORM which automagically generates and runs queries for you, but which doesn’t necessarily do it in the most efficient way possible.<\/p>\n

\"database-profiling.png\"<\/p>\n

Now by popular demand, we’ve added support for profiling MySQL (or MariaDB<\/a>) and PostgreSQL<\/strong>, so you can see queries run against those databases too.<\/p>\n

Some of you have also said that you’re using the Devart dotConnect data providers instead of the native .NET ones, so we’ve added support for those drivers too. Hope it helps!<\/p>\n

For the record, here’s a list of supported connectors (ones in bold are new):<\/p>\n

SQL Server<\/p>\n