Sorry for the delay for part 3. I have not been able to take our existing standard reports and make them work properly in a Reporting Services environment. I’m going to release the files anyway, in case one of you can figure out what is wrong. I’m not a Reporting Services guru, but I hope that somebody out there can find the bug and let us all know. (I think the problem is in the extraction tool that we used to dynamically localize them into US – English.)
Please see the attached zip file containing all of our standard reports. You can view them in Business Intelligence Development Studio and look the queries behind them… but for some reason, some (original Disk Usage.rdl for example) will not run out of the box.
Here are some descriptions of parameters for the reports:
CLR data type
The type of object. For example, “Database”, “Login”, “Functions”.
The name of the object. For example, “Foo”, “AdventureWorksDW”, “GetUserIDFromName”, etc.
Used in the Default report to show error information.
This was used to indicate whether the dataset being passed from OE is filtered or not. We will respect the filters the user has in place in OE and this parameter allows us to indicate on the list reports whether the list is filtered.
Name of the server and instance currently connected. In the form of “server\instance” for a named instance and “server” for a default instance.
Prompt Name: ServerName
Allow Null: checked
Allow Blank: checked
Avail Values: none
Name of the font to be used to display the report.
Defaults: Non-Queried – “Tahoma”
Name of the database containing the current object. If the object is not database scoped, this value will be an empty string.
Please post a comment if you have any questions/suggestions.
Paul A. Mestemaker II
Microsoft SQL Server