Databases Reference
In-Depth Information
8.
Open your browser, and navigate to
https://[servername].reporting.windows.net/reportserver/AzureReport/Report1
9.
You should be presented with your SQL Reporting Service Home folder and the
AzureReport
folder listed. In the
AzureReport
folder is your newly created report. To view
the report, click the report link.
You've just walked through a simple example of creating a report that pulls data from SQL Database. However,
before we close this discussion of SQL Reporting, we also need to talk about security.
Security
This section contains some guidelines and best practices for managing the security of your SQL Reporting server
and reports.
•
When embedding reports into your application, secure your connection string to the
report server.
•
Because reports can only use SQL Database instance as a data source, the recommended way
to provide access to shared data sources is to create and deploy shared data sources for reports
to a folder on the report server. Store the credentials for each shared data source on the
report server.
•
By default, report items inherit security based on report folder permissions. Thus, the folder
to which you deploy your report items matters greatly. By assigning specific permissions to a
folder, you break the inheritance for permissions in the folder hierarchy.
SQL Reporting requires not only a username and password to access reports, but a URL as well. These three
pieces of information are the URL, username, and password to the report server account. However, you can create
users in the Management Portal and assign them to roles that grant permissions. You can then provide the report
readers with those usernames and passwords.
When creating new users, you assign them to Item roles, and optionally, System roles.
Roles
As part of creating new users, you also assign them to an Item role and, optionally, a System role. The Item roles and
System roles are similar to those available on a native mode report server:
•
Item roles: Browser, Content Manager, My Reports, Publisher, and Report Builder.
•
System roles: System Admin and System User.
Roles are a concept that helps organize in terms of functions or goals. Roles represent one or more people who
perform one or more functions or tasks that require specific permissions. For SQL Reporting, the preceding roles help
determine which users can perform specific functions such as viewing or editing reports, publishing reports, creating
and managing additional users, and managing database objects.
For example, the Browser role can run reports, subscribe to reports, and navigate through the folder structure.
The My Reports role can manage a personal workspace for storing and using reports and other items.
It should be noted that these roles are not specific to Windows Azure SQL Database, but to the underlying SQL
Server Reporting service. More information about these roles can be found here:
