• There isn't a good way to do this. SQL doesn't really track access of resources by user and aggregate it. It can track some things by resource accessed, but not really user.

    You could run a trace that captures users and just something like CPU or reads and then create some cost back calculation from that data.

    It's an interesting idea, and if you come up with something, I'd love to see you write something up on how you implement it.