I am new for RDCL 2008 format. I used RDLC 2005 format for a while and it works fine. However, recently, my company is changing to RDLC 2008 format from RDLC 2005 format. The original report rendering engine crashed. Because in RDLC 2008 format, the connection string and the query string became <ConnectString>/* Local Connection */</ConnectString> and <CommandText>/* Local Query */</CommandText>
Does any one know how change from
<CommandText>/* Local Query */</CommandText>
to something like <CommandText>select * from US001_USER</CommandText>?
Thanks!
I found the solution myself.
Actually, I was using VS 2010 to create RDLC 2010 format file. However if I use VS 2008 (with SSRS 10.0) to create RDL 2010 format file, the ConnectString and CommandText will be filled. RDL 2010 file is just simply changed to RDLC 2010 file by renaming the file.
You can also use Report Builder 2.0.
Report Builder 3.0 uses RDLC2010 which is only usable on a report server, not embedded using reportviewer control. MS promises a updated viewer.
Also see the GotReportViewer.com - They have a source for a program to read all the info... Bottom Right of page.
Related
I am using SSRS 2005 in an old project, it has been working perfect with ReportViewer in local mode for many years, but recently I encountered an exception while exporting the excel report. ".xls" file has a max rows limit (65536), I decide to upgrade the SSRS to a higher version.
Since many years past, there generated thousands of reports, the report definitions were saved as XML in the database. I tried to load the old report definition with ReportViewer 2010 (SQL Server 2008 r2), but failed.
After some research, I know it is easily to convert RDL 2005 to RDL 2010 by opening the report in Visual Studio, it did work as expected.
Is there a library or command line tool to convert RDL 2005 to RDL 2010?
I decided to rewrite the logic creating SSRS Report, basically it is translating business logic to a xml string.
BTW, I got this repository: dynamic-rdlc, it is much easier.
We have migrated our application and reports from SQL 2005 to SQL 2008 R2. After testing, we found that Excel format of the report in both SSRS 2005 & SSRS 2008 R2 is different.
We have fixed this in the RDL file and uploaded that file in SSRS 2008. So, from that day/time onwards the format is correct. But when we download the history reports from SSRS 2008, they are still showing report in older format.
Is there any way we can point history reports to refer latest RDL file so that older reports would appear in proper format.
Thanks,
It sounds like you are referring to the report snapshots history. When report snapshots are created they include the report definition as it was at the time the snapshot was generated, and so will always use this definition. This cannot be changed, so there is no way to alter the format of historical snapshots from before you changed the report definition.
More information: https://msdn.microsoft.com/en-us/ms156325.aspx
Sorry for being a newbie to SSRS.
My design goal:
Near term: develop - using SSRS - a simple client side (no reporting server!) report - based on MS SQL data tables, and embed it into the .NET WPF client (application)
Long term: for additional reports, hire external SSRS experts, so they will provide the reports developed, and I will integrate them into the same WPF application.
I managed to do 2 things:
Develop a simple report connecting to MS SQL, using Reports Builder 3.0 - as a result, an RDL file was generated (the file contains all the DB connections)
Embed a ReportViewer WinForms control into the WPF application.
Unfortunately, I wasn't able to load the report I developed, into the application.
I understood from articles on the new that RDL is not designed to support client-side execution (without a server), and RDLC should be used instead. However, I wasn't able to figure out how to conver the report to RDLC, using the Reports Builder - it does not give me an option to save in a different format.
I would appreciate any hint from the experienced people on how to accomplish my goal.
Specifically, should I use RDLC, and if positive - what's the way to get the report in this format?
Thanks
Max
I would recommend using Visual Studio when creating RDLC reports that will be embedded within an application and run in "Local" mode, and using either Microsoft Report Builder or Visual Studio to create RDL reports that will run in "Server" mode within SSRS.
A RDLC report would be created within a WPF Visual Studio project be simply creating a new Report.
A RDL report would be created within a Reports Server project when using Visual Studio.
Alternatively, it appears you could simply rename the file from RDL to RDLC if you don't mind manually correcting the Data Source information in the report definition file: http://msdn.microsoft.com/en-us/library/ms252109(v=vs.120).aspx.
I just started working with other developers. When they send .rdl files back to me and i try to open the file through visual studio 2005, it shows some raw html rather than the design view. The html says:
One or more errors encountered while loading the designer. The errors are listed below.
The Report element was not found.
How can i fix this?
For anyone who has the same problem, I figured it out:
The developers modified and saved using 'Report Builder'(v. 3.0). Report Builder 3.0 is designed to support SSRS 2008 R2 only and supports a new version of the RDL schema, which is not compatible with SSRS 2005. So, i had to use SQL Server 2008 R2 Reporting Services instead.
I have a report that has ~1k columns and ~17k rows and I'm trying to render it to Excel 2007 with SSRS 2008 R2 Nov CTP.
SSRS team members have mentioned in multiple places that Excel 2007 format is included in 2008 R2, for instance:
http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/69545568-73cb-4f4c-8f35-44472ba6d013
Now, it's certainly possible that it just hasn't made it into the product yet (at least as of Nov CTP), and if that's the case, that would be good to know, too (and ideally when it would be in the product).
The repro report and data (along with attempts showing the existing interface still does Excel 2003 format) are attached to the bottom of this blog post, FWIW:
http://cid-456117cf53a42144.spaces.live.com/default.aspx
Unfortunately, it looks like I was misinterpreting Jin Chen's answer ("Here, has good news, we have improved the ability in SQL Server Reporting Services 2008 R2") - there was an answer later by another member of SSRS that states that 2008 R2 will not support xlsx / Excel 2007 output:
http://social.msdn.microsoft.com/Forums/en/sqlreportingservices/thread/87cfd5d4-ea3c-4250-aab8-a1a3dffa3241
As far as a full featured Excel 2007 xlsx renderer, it is definitely on our list to build but it will be post SSRS 2008 R2.
So, maybe it was in R2 but got cut, but either way, it doesn't appear to be an option now.
For those who might be in a similar situation that run across this question on SO, if programmatically generated the spreadsheet is an option for you, I would recommend EPPlus.
http://epplus.codeplex.com/
Excel 2007-2010 format (Office Open XML) is the default rendering format in SQL Server 2012
http://technet.microsoft.com/en-us/library/dd255234.aspx