Databases Reference
In-Depth Information
Also from the ribbon, you have the ability to look at the report execution log. You are not limited to a time span
with this option. You can simply select start and end dates for which you want to view. The execution report can be
saved locally.
Pricing
Starting August 1, 2012, users of SQL Reporting are billed for using it. SQL Reporting use is charged for each clock
hour of a reporting instance (reporting server), a minimum of one reporting instance for each clock hour that a SQL
Reporting server is provisioned, even if no reports are deployed.
The price per reporting instance is $0.88 per hour per reporting instance. This charge covers up to 200 reports
each clock hour. For each clock hour during which more than 200 reports are generated, another Reporting Instance
Hour at $0.88 will be billed (for each additional block of 200 reports).
Summary
In this chapter you first learned what Windows Azure SQL Reporting is and the many benefits this cloud-based
reporting solution provides. This chapter then discussed the architecture of SQL Reporting and how this architecture
provides the high availability and scalability needed in a cloud-based reporting solution.
It's also important to understand the functional differences between on-premises SQL Server Reporting
Services and SQL Reporting, so we spent some time discussing these differences and how they might impact report
development.
Lastly, this chapter discussed provisioning a new SQL Reporting server, creating and deploying a report, and
the security around hosting reports in SQL Reporting. Much of the functionality is shared between on-premises
development tools and the Management Portal when developing reports, such as defining folders and data sources
and applying permissions. This provides great flexibility in report development.
