A script-enabled browser is required for this page to function properly.

About database roles

Database roles provide a way for end users to run reports that query tables to which they do not have access privileges. For example, a report may query a table that includes sensitive information such as salary data, even though the final report does not display this data.

Database roles are checked in the runtime environment only. If a table requires special access privileges, end users without those privileges cannot run a report that retrieves data from that table. However, if a database role is defined for the report, end users with privileges for that role can run the report using Reports Runtime (rwrun). Note:   To run a report for which a database role is defined, the end user must run the .rdf file, not the .rep file.   When running multiple reports, Reports Runtime automatically switches to the role defined for the current report.

If you try to open a report in Reports Builder for which a database role has been defined, you will be prompted for the role password. Typically, only the report designer and DBA have this information.

See also

Setting a database role