SQLClue includes many ReportViewer reports that run in the SQLClue Administrator's Console. There are also many Report Server Reports that can be executed using the SQL Server Business Intelligence Development Studio (BIDS) or optionally deployed to a Reporting Services server.
All reports are developed in BIDS as standard Reporting Services .rdl reports and then copied to a ReportViewer folder and simply renamed to the .rdlc extension for integration into the SQLClue Administrator's Console application. The Reporting Services .rdl reports and the ReportViewer .rdlc reports are included in the "SQLClue Application Resources" library that can be accessed from the SQLClue Program Group. Reporting Services .rdl reports from the "SQLClue Application Resources" are shown in [Image1]. In ReportViewer the DataSources in the reports are ignored. The application must supply the data. In exchange the application gains access to the events generated during report loading and drill-through. In Reporting Services the Datasources are required. In ReportViewer the user experience is richer, more interactive, and can integrated with other application components. In Reporting services the reports are read only and atomic with limited Drillthrough and Subreport capabilities. There are advantages to both ReportViewer and Reporting Services hosted reports.
[Image 1]
All Reporting Services .rdl reports are fully supported by Reporting Services from any Edition of SQL Server that can be used to host the SQLClue data stores including the freely distributed SQL Server Express with Advance Services. An existing remote Reporting Services server can also be used to host the Reporting Services reports. There is a considerable amount of functionality and interactivity lost when using Reporting Services instead of the embedded ReportViewer control. Nonetheless the reports provide a preferred mechanism for users wishing to produce custom reports or to distribute the data collected to a broader user base across the organizational intranet than can be securely supported through SQLClue Administrator's Console UI access.
One very powerful intranet use if the provided Reporting Services reports in the SQL Configuration Archive collection is the "SQLConfigurationChangeDefinitionByVersion.rdl" Publishing this report to a Reporting Services server that can read from the SQLClue repository and is accessible by developers provides the most time saving and effective way possible for developers to see the code that is running in a live environment without giving them direct access to that live environment. You can see this report in action by opening the SQL Configuration Catalog Report from the SQLClue Console "Reports" Menu. ([Image 2])
[Image 2]
The SQL Configuration Catalog consists of several reports and is integrated with the SQLClue Configuration Compare. This makes it possible to easily see exactly what changed between versions. You don't get that integration when using a Report Server. You also don't get the "Copy to Clipboard" capability. Instead, the standard export options available from the report server must be used. (If you prefer to give the developers those full compare and copy capabilities, consider replicating the SQLClue Repository to a location that can be used to host a SQLClue Console that the developers can use but that is not directly connected to the live system.)
This page is intended as a library of Reporting Services and ReportViewer reports contributed by
SQLClue users. When you have a report put together, Please
send it to me! Include a description of what the report does for you, the source of the data and any other information that would help others determine if the report may be useful for them. Also state if you would like your contact information posted with the report. All reports that I am able to validate will be posted to this web site.
This page was last modified on Tuesday, February 02, 2010 08:43:22 AM