I want to determine if some databases are overloaded or unbalanced, and think that looking at the transaction logs created per database over time would tell me which DB is at risk of missing RPO targets due to high IO (mostly writes).
My thought is to create a graph of each database, every X minutes and count each log that is created.
Since each log = 1MB in an E2010 DAG, I can easily calculate the amount of data that could be lost in a given time.
So my question is:
How can I determine if a given database has extra IO that might be better moved to a lower volume database? Is transaction logs a valid way of looking at it?
How should I procedurally figure out the load? Perhaps a powershell script, C#, and export that to a graph or excel.