A sample is displayed below: SSRS appears to use the data stored in the Properties column to detect paper size and orientation when printing the report.When creating a linked report, a new row is created in the Categories table, with the Link Source Id column set to the Id column of the original report you’re linking from.She also explains how to use the Report Builder to provide "self-service" reporting to end users, allowing them to build custom reports based on report parts and shared datasets.
Unfortunately, there is no facility in the Report Manager to directly set there properties, so one of the following needs to occur: A post on Brian Weckler’s blog provides VB.
NET code for connecting to the Report service and manually setting the properties: property field can be directly updated in the catalog table.
The code file contains two sample Visual Studio projects and a SQL Script for creating the .
You will not be creating any new reports from scratch in this article but instead using reports that were created in the Projects from Parts 1 and 3, all of which are included in the code download file.
Here are the steps to do this - I have used this tool successfully for more then one and half years to provide report deployment script to client with every release without facing any major issue.
I would highly recommend you to use this for deploying your reports on client machines.
The Properties column is initialized with the following: .
Since there is no property data, it uses defaults, generally 8.5×11.
this table holds the report location, the binary data for the report, as well as parameter and property information, among other things.
On deployment, various report properties are extracted and added to the Properties column of the Categories table in the Report Server database.
The most reliable way to resolve this is to delete the file associated with your report RDL file.