> you can almost always find a different way to store it that gives you richer information, if you need it.

The trade-off here is DB speed/size and the secondary information you can gather from that DB.

In my eyes, after a certain point the DB shall not be the place to query and rebuild past actions from scattered data inside it. Instead, you can delegate these things to a well-formatted action log, so you can just query that one.

Unless it's absolutely necessary, tiering sounds and feels much more appropriate than bloating a DB.