locked
ReportViewer control - Choosing between LocalReport and ServerReport RRS feed

  • Question

  • I'm going to use the ReportViewer control in a web page.   I'm trying to choose between using local reports (.rdlc file) and server reports.  Are there important pros and cons regarding these?

     

    Monday, December 27, 2010 4:13 PM

Answers

  • There was a similar discussion in this group previously. You can refer the same:  http://social.msdn.microsoft.com/Forums/en/vsreportcontrols/thread/1b06b84a-3c6e-40f1-908e-07e332a45a04  [ReportViewer control local and remote mode differences]

    Both Local Mode and Remote mode has their own advantages.. This is completely based on your requirement you can choose Local mode or remote mode of report processing.

    When to Use Local Processing

    Local processing mode is recommended for applications that include small to medium-sized reports and datasets. Because all data and report processing is performed on the client, you might encounter performance degradation or memory limitations if you attempt to process large or complex reports and queries.

    Local processing mode is less scalable than remote processing and is intended for standalone applications that do not require a report server. Users who are familiar with server reports that run on a remote SQL Server Reporting Services report server should note the following differences:

    • In remote processing mode, the report server both retrieves the data and processes the report, whereas in local processing mode, the ReportViewer control processes the report only, and the the host application must retrieve the data and supply it to the ReportViewer control.
    • Client report definitions do not include query information.
    • Report parameters in client report definitions (.rdlc) do not map to data source query parameters.
    • There is no parameter input area for a client report definition that accepts values that are subsequently used in a query

    When to Use Remote Processing

    Server-based reporting lets you centralize report storage and management, set policies and secure access to reports and folders, control how reports are processed and distributed, and standardize how reports are used in your business. Reporting Services can be installed in single-server, distributed, and clustered configurations. Consider using remote processing if your report has the following characteristics:

    • Report will be accessed by many users.
    • Report has a very complex query or contains a very large amount of data, resulting in system resource overload on the computer that hosts the application.
    • Report is already published on a report server, and you want to include it an application that you create and deploy.

     Reference articles:

    Hope this helps!

     


    Chaitanya
    Monday, December 27, 2010 5:21 PM

All replies

  • There was a similar discussion in this group previously. You can refer the same:  http://social.msdn.microsoft.com/Forums/en/vsreportcontrols/thread/1b06b84a-3c6e-40f1-908e-07e332a45a04  [ReportViewer control local and remote mode differences]

    Both Local Mode and Remote mode has their own advantages.. This is completely based on your requirement you can choose Local mode or remote mode of report processing.

    When to Use Local Processing

    Local processing mode is recommended for applications that include small to medium-sized reports and datasets. Because all data and report processing is performed on the client, you might encounter performance degradation or memory limitations if you attempt to process large or complex reports and queries.

    Local processing mode is less scalable than remote processing and is intended for standalone applications that do not require a report server. Users who are familiar with server reports that run on a remote SQL Server Reporting Services report server should note the following differences:

    • In remote processing mode, the report server both retrieves the data and processes the report, whereas in local processing mode, the ReportViewer control processes the report only, and the the host application must retrieve the data and supply it to the ReportViewer control.
    • Client report definitions do not include query information.
    • Report parameters in client report definitions (.rdlc) do not map to data source query parameters.
    • There is no parameter input area for a client report definition that accepts values that are subsequently used in a query

    When to Use Remote Processing

    Server-based reporting lets you centralize report storage and management, set policies and secure access to reports and folders, control how reports are processed and distributed, and standardize how reports are used in your business. Reporting Services can be installed in single-server, distributed, and clustered configurations. Consider using remote processing if your report has the following characteristics:

    • Report will be accessed by many users.
    • Report has a very complex query or contains a very large amount of data, resulting in system resource overload on the computer that hosts the application.
    • Report is already published on a report server, and you want to include it an application that you create and deploy.

     Reference articles:

    Hope this helps!

     


    Chaitanya
    Monday, December 27, 2010 5:21 PM
  • @Jhcorey,

    Please refer to Chaitanya's detail and professional reply, if you have any other question, please feel free to ask.

    Thanks,


    Challen Fu [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Wednesday, December 29, 2010 2:59 AM