SALES: 1-800-867-1380

Download an Execution Log (Azure SQL Reporting)

Updated: May 9, 2014

ImportantImportant
SQL Reporting will discontinue service on October 31, 2014. See this FAQ for details. For reporting on Microsoft Azure, visit Virtual Machines on WindowsAzure.com.

You can download the execution log from a SQL Reporting report server as a CSV file. The log can help you troubleshoot reporting problems and performance issues and learn about the overall health and use of your report servers.

The execution logs contain the same type of information as an SQL Server native mode report server execution log. For more information, see Report Server Execution Log (http://go.microsoft.com/fwlink/?LinkId=228111).

Summarized execution log information appears in the usage graph on the SQL Reporting dashboard in the management portal. The usage graph is updated periodically, within a few hours, but possibly as long as one day. To get information about report execution immediately, you should download the execution log.

  1. Open a Web browser, and launch the Azure Platform Management Portal by specifying the appropriate credentials. Open the SQL Reporting server.

  2. Click the name of the reporting service, and then click Dashboard.

  3. Click Download Execution Log below the usage graph.

    The Download Execution Logs dialog box opens. The default start and end dates are the preceding 3 days up to the current date.

  4. Optionally, type a different date or choose a different date in the calendar, up to 60 days from the current day.

    If the file is too large to download, an error will occur. See Known Issues (Azure SQL Reporting) for error resolution information.

  5. Click the checkmark to save your changes and download the file. You can choose whether to open or save the file to a location on your computer.

  6. An execution log with the specified name and path is created.

    noteNote
    The execution log might be empty. It is not possible to determine whether the log is empty before you download it. If there was no report rendered during the selected time range, the execution log is empty, and the column headers are not displayed on the downloaded CSV file.

  1. Navigate to the location where you saved the execution log.

  2. Right-click the file and open it in Excel or a text editor such as Notepad.

    The following is an example of a very brief execution log. The log has only one row. Depending on activity level on the report server and the time span of the execution log, the execution log might have thousands of rows.

     

    ItemPath UserName ExecutionId RequestType Format Parameters ItemAction TimeStart TimeEnd TimeDataRetrieval TimeProcessing TimeRendering Source Status ByteCount RowCount AdditionalInfo

    /Sales

    Admin1

    hfqtaweujl2mriadyytfy345

    Interactive

    RPL

    ShowInfo=False

    Render

    8/12/2011 8:04:35 PM

    8/12/2011 8:04:46 PM

    579

    1422

    6097

    Live

    rsSuccess

    2312

    16

    <AdditionalInfo><ProcessingEngine>2</ProcessingEngine><ScalabilityTime><Pagination>0</Pagination><Processing>0</Processing></ScalabilityTime><EstimatedMemoryUsageKB><Pagination>0</Pagination><Processing>31</Processing></EstimatedMemoryUsageKB>

    noteNote
    The AdditionalInfo field is an XML property bag or structure containing additional information about the execution. For more information about the fields of an execution log, and AddtionalInfo, see Report Server Execution Log (http://go.microsoft.com/fwlink/?LinkId=228111).

See Also

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft