Concise, clear explanation of how to implement blockchain auditing verification among other features. Thanks, going to check out the white paper! Cool, cool, cool as they say ;)
I'm trying this out and have a dumb question. With append-only, how do you do retention control? If you can't DELETE, then how do you, say, kill logs older than a year? or are you doomed to have an ever-expanding table with no way for size control?
Hi Anna and Jason. I viewed the documentation for Ledger tables but let's say I only need to store historical data for a year or so. How do I ever get rid of old data in the history table? Or am I stuck with an ever growing database, hoping that storage costs decline faster than my database grows?
This is amazing.
This is SO useful. Amazing work
Concise, clear explanation of how to implement blockchain auditing verification among other features. Thanks, going to check out the white paper! Cool, cool, cool as they say ;)
What a very pleasant surprise. You both Rock. Thank you!
Perfect Jason . Thanks for short and sweet demo. I leaned interesting topic..
Just an amazing way to simplify what actually is complex, now Ledger is GA for Azure SQL Database, which makes even more secure the SQL databases
I'm trying this out and have a dumb question. With append-only, how do you do retention control? If you can't DELETE, then how do you, say, kill logs older than a year? or are you doomed to have an ever-expanding table with no way for size control?
yes...this is awesome idea...
Hi Anna and Jason. I viewed the documentation for Ledger tables but let's say I only need to store historical data for a year or so. How do I ever get rid of old data in the history table? Or am I stuck with an ever growing database, hoping that storage costs decline faster than my database grows?
Same situation here. Found any way for retention control?
A definition of immutable & non-repudiation would probably be helpful for people with english as a 2nd language