Help on Storage transaction calculation RRS feed

  • Question

  • Hi,

    Would you be able to confirm that, if there are e.g. 50 telemetry points in a blob, accessing all of those telemetry points would only constitute 1 transaction (because it is only one read operation to one blob).


    Tuesday, March 1, 2016 2:32 PM

All replies

  • Hello,

    Transactions – Each individual Blob, Table and Queue REST request to the storage service is considered as a potential transaction for billing.

    Applications can then control their transaction costs by controlling how often and how many requests they send to the storage service. We analyze each request received and then classify it as billable or not billable based upon our ability to process the request and the request’s outcome.

    Here are a few examples:

    • A single GetBlob request to the blob service = 1 transaction
    • PutBlob with 1 request to the blob service = 1 transaction
    • Large blob upload that results in 100 requests via PutBlock, and then 1 PutBlockList for commit = 101 transactions
    • Listing through a lot of blobs using 5 requests total (due to 4 continuation markers) = 5 transactions

    For more information on understating storage billing, please refer the link below: Understanding-windows-azure-storage-billing-bandwidth-transactions-and-capacity

    Windows Azure Storage Logging provides a trace of the executed requests against your storage account (Blobs, Tables and Queues).  It allows you to monitor requests to your storage accounts, understand performance of individual requests, analyze usage of specific containers and blobs, and debug storage APIs at a request level.

    For more details on Windows Azure Storage Logging please check the link below:


    For more information on pricing details, please check the link below:


    Wednesday, March 2, 2016 8:57 AM