What is the most efficient way to determine whether row or page or columnstore compression (or none) would be most effective for each index in an Azure SQL Database (standard or premium tier) used for OLTP, where sp_estimate_data_compression_savings is not supported?

I realize that whether doing so is good for performance would depend on the frequency and volume of writes for each index. What other considerations should be taken into account?

(I realize that whether to use columnstore for a partitioned index is a complex issue and I'll consider that out of scope for this request.)

1 Answer 1


Kalen Delaney has created a version of sp_estimate_data_compression_savings specifically for this use case.

Its available for download from the corresponding blog post here.

  • Thanks! It seems odd that a Google search for the sp name and "Azure SQL Database" wasn't turning up that blog post, but now it turns up this StackExchange page that has the pointer to Kalen's post. Oh well, at least it is more easily found now. For anyone interested in this, please upvote: feedback.azure.com/forums/908035-sql-server/suggestions/… Commented Jan 7, 2019 at 14:05
  • Looks like the link is dead
    – Clement
    Commented Mar 22, 2022 at 6:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.