Using the management portal (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.|
You can manage SQL Reporting through the . In the management portal, you can add SQL Reporting to new or existing subscriptions.
Using the Azure Platform Management Portal, you can connect to any service instance that exists for your subscription. The management portal provides a dashboard that displays information about the service, including subscription information, the Web service URL, the name of the server administrator, the region in which the server was created, and report usage. From this page, you can download the execution log as a .csv file and view it in Excel.
The management portal provides access to management tasks, including uploading reports, creating data sources, managing permissions, and so forth. The portal also makes it easy to switch from server to server and view information about a server and the server content.
To organize reports and data sources in a useful way, you can create folders on the report server.
The following illustration shows SQL Reporting in the .
For more information about the , see Azure Management Portal (http://go.microsoft.com/fwlink/?LinkId=252537).
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. For more information, see Accounts and Billing in Azure SQL Reporting (Azure SQL Reporting).
The portal provides easy access to common deployment and management tasks, with pages for viewing report server information. For each service instance, you can manage users and permissions, create the shared data sources that reports use, create folders, and upload reports.
You can create one instance of SQL Reporting service in each region per subscription. Each region has one datacenter and the terms region and datacenter are often used interchangeably. It is highly recommended that SQL Reporting report server and the Azure SQL Database database that contains the report data be located in the same region. Also, if you store images used in reports in a database, you should consider the location of that database. You can save money by placing the report server and that database in the same region.
To delete a report server from the management portal, select a server and click Delete. When you delete the report server, its Web service URL, the Reporting Services databases (reportserver and reportservertempdb), are also deleted. You cannot restore the report server after you delete it.
The main page for SQL Reporting displays a list of all the reporting services created under the current subscription. Click a report server to view information about the server. Each service has a Dashboard, Users, and Items page.
On the Dashboard, you will find usage information and the following details:
Web service URL—Web service endpoint URL that you use to access and reports and other items on the server and run reports. [Link] opens the report server using this URL. If you are not signed in, the SQL Reporting logon page opens and you must sign in before you can access the server; otherwise, the report server opens. If you want to use the URL that displays in the portal, select the URL and then copy it.
User name—User name you used to log in to the server.
Region—Region that you selected when you first created the report server.
For more information about running reports on the server, see Run a Report (Azure SQL Reporting) and Access a Report Server by Using a URL (Azure SQL Reporting).
The SQL Reporting portal provides user interface that make it easy to manage users and their permissions. You open most dialog boxes from the toolbar.
View users and their permissions. Use the Manage Users dialog box to view a list of server users and search to find specific users. To open this dialog box, click USERS in the main page, and then click CREATE.
Create new users, assign them an item role. Item roles are identical to those available on a native mode report server. For more information, see Using Predefined Roles (http://go.microsoft.com/fwlink/?LinkId=228113), Role Assignments (http://go.microsoft.com/fwlink/?LinkId=228114), and Tasks and Permissions (http://go.microsoft.com/fwlink/?LinkId=228115).
Use the Create User dialog box to create new users and assign them to roles. Open this dialog box from Manage Users.
Delete users. Confirm deletion in Delete User. Open this dialog box from Manage Users.
Note The report server administrator, specified when you first create the server, cannot be deleted.
Change user passwords. Use Change Password to change passwords. Open this dialog box from Manage Users.
For more information, see Manage Users (Azure SQL Reporting).
There are two ways to add shared data sources to a SQL Reporting reporting service: deploy them from SQL Server Data Tools, or create them using the management portal.
Use the Create Data Source dialog box to create a data source. To open this dialog box, click ITEMS in the main page, and then click ADD, followed by Create Data Source.
The properties that you specify in Create Data Source are the same as the ones you specify when you create a data source in BI Development Studio or Report Manager. The only differences are options not applicable to SQL Reporting are absent. For example, you can choose only the Microsoft SQL Azure data source connection type. For more information about creating data sources in BI Development Studio and Report Manager, see Data Connections, Data Sources, and Connection Strings (SSRS) (http://go.microsoft.com/fwlink/?LinkId=228112).
After you deploy or create data sources you can update their properties and permissions. The context menu on a data source provides access to data source properties and permissions. You can also access data source properties by clicking the data source in the Data Source list.
|You cannot update embedded data sources. Instead, you must download the report, update the data source in Report Designer in SQL Server Data Tools and then upload or deploy the report again.|
You can upload or deploy any RDL report to SQL Reporting. Uploaded reports are not verified in the rigorous way that deployed reports are. To ensure the uploaded reports run successfully in the cloud, there are a few rules that report authors must follow. For more information, see Create reports for SQL Reporting.
By design, credentials for embedded data sources are removed from the report when you upload it. When you run the report you will be prompted for data source credentials. When you upload reports that use shared data sources, you need to deploy the data source before you upload the reports. The upload process binds the report to the data source, enabling the report to use the data source. If you reverse the order, the data source is not bound to the report and the report fails. If you want to upload the same report multiple times to the same folder, you must first delete the existing copy of the report the SQL Reporting report server or use a different report name.
Use the Upload Reports dialog box to upload reports. To open this dialog box, click Upload in the Report category on the taskbar. For more information, see Upload a Report (Azure SQL Reporting).
After you upload a report, you can update its permissions and some properties. For more information, see Update Permissions (Azure SQL Reporting) and Update Properties of Folders and Reports (Azure SQL Reporting).
You can use folders to organize and manage reports and data sources on the report server.
|See Known Issues (Azure SQL Reporting) for information about folder navigation and limitations in this release.|
Create folders to organize reports and data sources meaningful ways. Optionally, provide a description of folder content.
Upload reports to a folder.
Create shared data sources within a folder.
Download reports from a folder.
Delete a folder and its content.
Use the Create Folder dialog box to create folders. To open this dialog box, click Items in the main page. For more information, see How to: Create a Folder (SQL Reporting).
After you create folder, you can update the folder name and description and permissions on the folder. For more information, see Update Properties of Folders and Reports (Azure SQL Reporting) and Update Permissions (Azure SQL Reporting).
You can download the execution log for a report server as a CSV file. By specifying the start and end dates, you can narrow the scope of the log. You can also specify the location and name of the execution log.
Use the Download Execution Log dialog box to download an execution log. To open this dialog box, click Download in the Execution Log category of the taskbar.
For more information, see Download an Execution Log (Azure SQL Reporting).
A reporting service exposes items in a folder hierarchy that you define. The root provides a starting point, but from there you can create additional folders to organize and secure reports and shared data sources.
|The current release has limitations on the number of folders you can create and access in the management portal. For more information, see Known Issues (Azure SQL Reporting).|
This section lists procedures that show you how to do tasks by using the user interface that the SQL Reporting portal provides.
Create a Reporting Service (Azure SQL Reporting)
Manage Users (Azure SQL Reporting)
Download an Execution Log (Azure SQL Reporting)
Upload a Report (Azure SQL Reporting)
Run a Report (Azure SQL Reporting)
Download a Report (Azure SQL Reporting)
Update Permissions (Azure SQL Reporting)
How to: Create a Folder (SQL Reporting)
Update Properties of Folders and Reports (Azure SQL Reporting)
Create a shared data source (Azure SQL Reporting)
Edit a shared data source (Azure SQL Reporting)
Understand SQL Reporting usage (Azure SQL Reporting)
Other ResourcesGetting Started with SQL Reporting