Feature of Azure SQL that uses cryptographic digests so any tampering with table history can be detected. Masking and encrypting data are not part of it.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Ledger in context, with comparison tables and the common traps.
Terms in this definition
Related terms
- Database digest
Represents the state of all ledger tables in a database as one hash of the ledger's newest block. You can store it by hand or have it saved automatically to Azure Confidential Ledger or immutable Azure Blob Storage, then use it to verify the ledger later.
- FILESTREAM
Lets SQL Server keep varbinary(max) data as ordinary NTFS files that still stay transactionally consistent with the database. TDE doesn't encrypt this data, and ledger tables can't use it.
- Ledger database
With LEDGER = ON set at creation, the entire database becomes tamper-evident: all its tables must be ledger tables, which are updatable unless specified otherwise.