How do I compress the reporting service response in SSRS 2012 RRS feed

  • Question

  • Hi,

    I am migrating the SSRS reports from 2005 to 2012.

    SSRS 2005 was using IIS, so the compression settings at IIS were sending the response of the report in compressed/gzip format, therefore the response size was small and report rendering is faster.

    When I move to SSRS 2012, it is using its own Http.SYS and doesn't use IIS. response size of the report is too large for the large reports and taking lots of time to render in the report viewer/browser.

    when I check through fiddler, for 2005 version, Transport: content Encoding = gZip

    However for SSRS 2012 its not compressed. body size of the response is more than 10 MB vs KBs in SSRS 2005.

    How do I compress the response of SSRS 2012 report when viewed in report viewer/browsers?

    Appreciate your quick response!!


    Nitin Nigam

    Barclays, Pune

    /Nitin Nigam Pune

    Thursday, July 16, 2015 8:51 AM


All replies

  • Hi Nitin,
    Thank you for your question. 

    I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated. 

    Thank you for your understanding and support.

    Best regards,
    Qiuyun Yu

    If you have any feedback on our support, please click here.

    Qiuyun Yu
    TechNet Community Support

    Friday, July 17, 2015 9:45 AM
  • thanks Qiuyun,

    let me know if you find any solution for this.

    /Nitin Nigam Pune

    Monday, July 20, 2015 4:18 AM
  • I too wish compression were a feature that was added to the http.sys. The only thing i've found to combat this is in the link below. I haven't implemented myself but it's worth a look.

    I put in a suggestion to Microsoft to add the feature, feel free to use the link below to vote.

    • Edited by JJordheim Monday, July 20, 2015 2:02 PM
    Monday, July 20, 2015 1:41 PM
  • Hi Nitin,

    Unfortunately this is a known limitation of the product. Please check the following link. Also in the link, it provides some possible workaround methods.



    Monday, July 27, 2015 8:15 AM