How to trigger a Azure SQL Database with Ledger tables verification failure

Joseph Chustz 0 Reputation points

We are planning to showcase the capabilities of Azure Ledger Technology to our financial services group. However, we are facing a challenge when it comes to demonstrating a database verification failure due to the manipulation of the ledger. The tables in the ledger are read-only, which restricts us from showcasing this particular aspect of the technology.

Is there any recommended approach or workaround that would allow us to simulate a database verification failure to showcase the robustness and resilience of Azure Ledger Technology, despite the read-only nature of the ledger tables? We would greatly appreciate any guidance or suggestions on how to overcome this limitation and effectively demonstrate the technology's capabilities in such scenarios.

Azure SQL Database
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. GeethaThatipatri-MSFT 29,012 Reputation points Microsoft Employee

    @Joseph Chustz Welcome to the Microsoft Q&A forum, Thanks for posting your question.

    Simulating a verification failure is indeed hard to do in Azure SQL Database. The fact that you are using append-only tables doesn’t make any difference compared to updatable ledger tables.

    Unfortunately, there is no option to tamper with the data files because you don’t have access to them.

    If the verification would fail, that would mean that potentially Microsoft has tampered with the data, which is something we want to avoid of course.

     An alternative could be to tamper with the digest file, but that is of course only for demo purposes. Digests should be stored on immutable storage so that it’s impossible to tamper with these as well.

    I hope this information helps. let me know if you have any additional questions.