When publishing a reporting services report. Where does the actual .RDL file sit on the server?
I can redownload the .RDL file via browsing through the report manager? But where is this file situated on the reporting services server?
Thanks
rdlreportingreporting-services
When publishing a reporting services report. Where does the actual .RDL file sit on the server?
I can redownload the .RDL file via browsing through the report manager? But where is this file situated on the reporting services server?
Thanks
From my experience there are few things to think about both things:
I. RDL reports are HOSTED reports generally. This means you need to implement SSRS Server. They are a built in extension of Visual Studio from SQL Server for the reporting language. When you install SSRS you should have an add on called 'Business Intelligence Development Studio' which is much easier to work with the reports than without it.
R eport
D efinition
L angauge
Benefits of RDL reports:
Downsides:
II. RDLC reports are CLIENT CONTAINED reports that are NOT HOSTED ANYWHERE. The extra c in the name means 'Client'. Generally this is an extension of the RDL language meant for use only in Visual Studio Client Applications. It exists in Visual Studio when you add a 'reporting' item.
Benefits of RDLC reports:
Downsides:
Honestly I like both for different purposes. If I want something to go out to analysts that they use all the time and tweak for graphs, charts, drill downs and exports to Excel I use RDL and just have SSRS's site do all the legwork of handling the email distributions. If I want an application that has a report section and I know that application is it's own module with rules and governance I use an RDLC and having the parameters be smaller and be driven by the decisions the user made before getting to the report part of what client they are on and site and then they usually just choose a time frame or type and nothing more. So generally a complex report I would use RDL and for something simple I would use RDLC IMHO.
I hope that helps.
TL/DR Version: Reporting Services is not giving you the correct RDL.
Your question prompted me to further investigate a suspicion I already had on SSRS for quite some time: report parameters can behave in unexpected ways for report developers when deploying (or downloading) report definitions. One related scenario I had noted before:
In short, if you want to update parameter settings for deployed reports you'll first need to delete it and then deploy it, or update the settings directly via the report manager.
Back to your question(s). You're not missing anything, this just seems the way SSRS is behaving (intended or not). The RDL schema has this (abbreviated) piece:
<xsd:complexType name="ReportParameterType">
<xsd:choice minOccurs="1" maxOccurs="unbounded">
<xsd:element name="DataType">
<!-- abbreviated -->
</xsd:element>
<xsd:element name="Nullable" type="xsd:boolean" minOccurs="0"/>
<xsd:element name="DefaultValue" type="DefaultValueType" minOccurs="0"/>
<xsd:element name="AllowBlank" type="xsd:boolean" minOccurs="0"/>
<xsd:element name="Prompt" type="xsd:string" minOccurs="0"/>
<xsd:element name="ValidValues" type="ValidValuesType" minOccurs="0"/>
<xsd:element name="Hidden" type="xsd:boolean" minOccurs="0"/>
<xsd:element name="MultiValue" type="xsd:boolean" minOccurs="0"/>
<xsd:element name="UsedInQuery" minOccurs="0">
</xsd:choice>
<xsd:attribute name="Name" type="xsd:normalizedString" use="required"/>
</xsd:complexType>
So, there should be a "Hidden" element for your ReportParameter.
I just verified your findings (in SSRS 2008), and think I may have the answer to your second question: SSRS is indeed not coughing up the correct version of the RDL. It's missing various bits about the parameters, including the element on being hidden or not.
Funny thing is: if you change the report in BIDS and set the parameter to hidden, the RDL will be changed and have the <Hidden>true</Hidden>
element.
Best Answer
It is not a file on the server. It stored as a BLOB in the ReportServer database.
(In the Catalog table to be precise on SSRS 2005)
Extended Answer