Blockchains do not delete records, etc. Also, you have to pay pretty much real money to put your record there. So we can have a good aproximation of what can happen with your proposal even if you need to pay extra for it.
Ethereum [1] routinely accumulates around 300G per year and routinely hits over one terabyte of data to sync. Remember, this is the size of the data to sync/transmit, not size of the data that is stored, which we may safely assume to be several times more, because of indices, etc.
Also, your proposal makes two tier database system: one that maintains current consistent view of the state and another for log purposes. The logging system needs high throughput storage with key range read request, which makes it, well, another pretty much fully fledged database (SELECT...GROUP BY...ORDER BY is needed).
The reason nobody does what you described because it is really prohibitive in storage space aspect and really is quite complex - a database on top of another database.
[1] https://ycharts.com/indicators/ethereum_chain_full_sync_data...
Ethereum [1] routinely accumulates around 300G per year and routinely hits over one terabyte of data to sync. Remember, this is the size of the data to sync/transmit, not size of the data that is stored, which we may safely assume to be several times more, because of indices, etc.
Also, your proposal makes two tier database system: one that maintains current consistent view of the state and another for log purposes. The logging system needs high throughput storage with key range read request, which makes it, well, another pretty much fully fledged database (SELECT...GROUP BY...ORDER BY is needed).
The reason nobody does what you described because it is really prohibitive in storage space aspect and really is quite complex - a database on top of another database.