First things first: if you cannot modify ASP.Net code, you cannot realistically use AOP - it would be a huge security hole if you could inject functionality into an application in this way.
Secondly, even a moderately busy web application will be generating a lot of database queries. It's not uncommon for a single page request to require dozens of database queries (many hopefully cached!), and for a single server to handle dozens or hundreds of requests per second; 100s of database requests per second is not unusual.
Thirdly, anything you do that slows down those database requests will almost certainly slow down the web application, possibly to the point where it will seem broken.
So, what can you do?
If you can modify the ASP.Net code, you could follow the advice in this question. It's trivial to implement, and is by far the cleanest option.
Pretty much every RDBMS engine has a "tuning" solution, which allows you to look at (live) queries against a database. These tools are optimized for tuning, and therefore unlikely to affect performance of the web application.
You could sniff the network traffic between the database and the server. Wireshark supports several database formats.