In GCP it'll be a two step process:
You should be able to create Log Filters:
And then use those log filters to create metrics:
This won't be as flexible or seamless as a SQL query, but the filters should provide you with ...
Your second approach seem to be the best. Having a Message entity with key relations to sender/reciever.
As for you deleting a user dilema, you should consider not removing the entity when a user is deleted as this would break your db consistency. You should probably just have a logic deletion (eg a boolean value changed when a user is deleted), that way, ...
To expand on Dan's answer with some detailed info:
If you have the option setup a small Linux server at home. You might have to modify the sshdconfig to allow for setting up SSH tunnels depending on your release. You might also need to modify the firewall config to allow port 22 connections, though most distributions do this automatically now when you ...
I have compile a summary of MySQL limits. Some, related to your question:
An InnoDB partition is limited to 64TB (2**46 bytes).
A MyISAM table is limited to 2** 56 bytes, but you need to change a setting to get beyond 2**48.
A table can have 1024 partitions until some recent release, then 8192.
(BIGINT is not relevant in these limits.)
Is there alarm?
This msdn walkthrough should have everything you need to accomplish what you want to do on the SSRS 2005 side. Pay attention to the section on setting up for remote smtp. Especially the part about setting SendUsing to 2.
This google guide provides the steps to configure things on their end.
The setup for SSRS 2008 isn't much different.
It seems to me your problem is that you are trying to test performance metrics that are not well supported in the underlying db. This makes it very difficult to compare performance across systems because the underlying approaches are very different. I don't think it is possible to do apples to apples comparisons just as I don't think you can do an apples ...