Export (0) Print
Expand All

Accounts and Billing in Azure SQL Reporting (Azure SQL Reporting)

Updated: May 9, 2014

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.

SQL Reporting is available to subscribers of Microsoft Azure. Like other services on the Microsoft Azure Platform, SQL Reporting is designed to support elastic scale. Based on your usage and seasonal requirements, you can easily and quickly add subscriptions and report servers to extend the capacity of your SQL Reporting environment and delete subscriptions and servers to decrease it.

You can use a calculator to quickly determine the cost of running a reporting instance for a set number of hours. For more information, see Azure Pricing Calculator.

You cannot turn on a reporting service for only a specified period of time. The service runs until you delete it.

Billing starts as soon as you create a reporting service and stops when you delete it. Each reporting service that you create is billed at a flat hourly rate, even if no reports are hosted on or rendered by the service. For example, if the rate is $0.16 per hour, the cost of running the service is $3.84 per day even if you never run a single report (see Pricing Details for the hourly rate).

The hourly rate increases as you increase the number of report executions. The first thirty report executions are built into the flat hourly rate. An additional charge (of the same low hourly rate) is applied for each additional 30 report executions. Notice that the charge is not per report, but rather per report pack, where a report pack is 30 executions. This means that if you run forty reports in one hour, you will be charged $0.32 for that hour ($0.16 at the flat hourly rate that includes the first thirty report executions, and an additional $0.16 for the next ten report executions).

SQL Reporting billing is based on clock hours, and a clock hour is defined by a round hour (from 00 minutes to 59 minutes). For example, if you render 5 reports at 10:50 AM and 6 more at 11:10 AM, each one counts towards the 30 executions that are part of each clock hour. The 5 reports that ran during 10:50 AM to 11:00 AM are part of the 10:00 to 11:00 clock hour, and the 6 reports that ran at 11:10 count towards the 11:00 AM to 12:00 PM clock hour.

You can check on current charges in View my bill. The billing system receives billing information for all the servers aggregated by subscription, including SQL Reporting. To open the page, click the sign in name at the top of the portal to roll down a list of subscriber options. View my bill is in that list.

The service is billed at an hourly rate that goes up incrementally after each set of thirty report executions. The following list explains which actions count as a billable event.

  • Open a report via its URL or through the portal.

  • Open a cached report (caching speeds up performance, but does not reduce costs).

  • Press Ctrl-5 or click the browser refresh button. Reloading a report counts as a new report execution.

  • Running a report with a unique combination of input parameters. For example, suppose a report prompts the user to provide a customer code as input. Each report execution using a unique customer code counts as a separate report execution. Also, clicking View Report again, even if you are using the same combination of parameters, counts as a unique, new report execution.

  • Clicking Save as and saving the report as a local file counts as a unique, new report execution.

  • Rendering an HTML report into a different format (such as PDF) counts as a new report execution.

The size of a report is not a factor in billing. Whether you render a very large multi-page report, or a small report, the billable event is rendering a single .rdl file.

Subreports, which are independent reports that you embed within a larger report, are not counted as separate executions. For example, if you have a main report that contains 5 subreports, you are charged for one report execution, and not 6.

SQL Reporting shows a history of server usage. You can keep track of current usage by monitoring usage data in the portal. For more information, see Understand SQL Reporting usage (Azure SQL Reporting).

See Also

© 2014 Microsoft