First of all, to track this, you need to set things up. This is nothing that SQL Server tracks by default, as it would add quite a bit of overhead.
There are a couple of options:
- SQL Server Audit.
- Extended events and capture the events sql_batch_starting and rpc_starting.
- Trace and capture the corresponding events.
All of these can have serious impact on the throughput on a system that runs many short queries. On such a system, they would also produce too much data for it to be useful.
Then again, if users only can access the database through the application, it makes more sense to have the auditing in the application, as the application knows what the overall operation is.