We are evaluating REDIS vs SQL Server for session state. During testing, we found that data in REDIS is not readable. It looks like encrypted with assembly information or maybe it is showing an error. This issue is occurring when Key has _Data as a suffix. The keys with _Internal as suffix are working fine.

enter image description here

However, When Sessions are stored in the SQL database then it shows clean and readable data.

So, My question is: is it expected behavior or there is something wrong? if it is wrong then where should I look to resolve this problem.

  • REDIS serializes anything (binary) whereas SQL session state requires things to be serializable (to text). This is why you can read everything stored in SQL. There is nothing wrong otherwise. Avoiding having to serialize (like REDIS does) is actually more efficient/less demanding.
    – Mark Cassidy
    Commented Aug 3, 2021 at 18:06

1 Answer 1


Looks to be influenced by Redis compression setting on top of binary format:

You configure the compression attribute to true to enable compression of session state data. Compressing session state data reduces the amount of data that you need to transfer between the Sitecore instance and the Redis database but might cause some additional CPU overhead.

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.