Pie charts seem to have this ability of grouping small series together into an "Other" group.
https://learn.microsoft.com/en-us/sql/reporting-services/report-design/collect-small-slices-on-a-pie-chart-report-builder-and-ssrs
How would you do this for a stack chart?
I'm working from a dataset that calls a stored procedure, which I have no access to (I don't have the password). I actually have to deploy the report to even test it, so manipulating the SQL is out of the question.
Thanks!
Related
I currently have a working SSRS report in Microsoft Report Builder. The report displays both a table of the data as well as a graph of the table. What I am trying to do is make it possible for the end user to be able to filter out or turn off visibility for one or more of the series on the graph.
Here is what I am thinking as a possibility: create an "Exclusion List" list parameter in which the user can enter series names that they'd like to filter out. Then I'd modify the graph's series' filter properties such that any series with a name present in the list parameter will be filtered out.
I haven't figured out fully how to implement the above, but it seems doable to me. However, I am wondering if anyone has a simpler solution to this problem? Any suggestions would be greatly appreciated.
I have more than 15 sub reports in my ssrs report.Each sub report should be displayed only when we click on some text to toggle.But in the background(SQL Profiler) is running all the sub report datasets along with the main dataset which is resulting in poor performance.I have gone through different procedures suggested in diff blog but did not find the right solution.
Can someone please help me with this.
Thanks,
Dev
Unfortunately, according to this documentation, subreports are run at the same time as the main report:
https://msdn.microsoft.com/en-us/library/dd207141.aspx
The "Performance" section of the above documentation (pasted below) makes a good point, but it would require a slight re-design (but end up with better performance!):
Performance
When deciding which to use, consider using a data region instead a subreport, particularly if the subreport is not used by multiple reports. Because the report server processes each instance of a subreport as a separate report, performance can be impacted. Data regions provide much of the same functionality and flexibility as subreports, but with better performance. Drillthrough reports have better performance than subreports, too, because they don't retrieve all the data at the same time as the main report.
I have excel sheet with monthly sales/cost data. Every month I use excel to generate all sort of graphs and then publish them as a pdf. But I want others to be able to play around with the different data they have on the graphs. I want to publish reports on webpage which generate charts based on a table when it loads up.Then, I want the users to be able to use buttons or sliders to change the range of the dataset (mostly having dates or quaters or product type etc) and then the charts to update with the new results.
Also, can anyone help me find the equivalent of this doc for sql 2008? I am looking for charts like This
I did some reading and found that SSRS can create all the charts that Excel can do. But I don't know if it can do all the calculations as well?
I also read we can make pivot tables in sql but am not sure if they are the same as the ones in excel where we can use them to filter data and the graphs show the changes real time.
I also read about MS Chart Control using ASP.net but I don't know asp and I don't know how much would researching about it help me in my case.
I just want my visitors to be able to manipulate the dataset that is generating them graphs on their visit. Thats it. Dont' want to store their changes or anything.
What do you guys recommend?
btw I have sql 2008 in mind to do this.
Do you guys recommend me to use Access 2007
Do they need to view the report on a webpage or could it open in Excel (or the Excel IE browser plugin)? SoftArtisans OfficeWriter has the ability to design rich Excel reports for SSRS with a template-based approach. The output will be a true Excel file with live charts, formulas and pivot tables that can be manipulated by the user. The out-of-the-box Excel export functionality doesn't have real formulas and charts.
Disclaimer: I work for SoftArtisans
Excel Charts and ability to dynamically customize is a pretty advanced feature compared what is provided in SSRS... Matrix is the equivalent of pivot in SSRS. You can follow this MSDN article to get an idea of Tables, Matrices, and Lists (Report Builder and SSRS). This can be helpful in terms of Reproduce an Excel Pivot table in SSRS 2008
Here is a better tutorial if you could take a look..
The most important aspect would be:-
Set Datasource to Chart Control
Define Fields to be used by Chart Control
Using parameters would be the best catch on filtering datasets. So you will need to have a secondary dataset on top of the main dataset.
How to filter one dataset value with another dataset Table value in SSRS.
References:
Can SSRS use pivot tables such like excel drag and drop
http://social.msdn.microsoft.com/Forums/en/sqlreportingservices/thread/4b4664e2-415b-41d4-99e6-1421aa70e7ac
I'm new to SSRS and I need the ability to group multiple reports into a single report. I've searched around a lot but not found much. I currently have two reports (more to come) that users need to be able to view/save individually. The users also need the option to view both those reports as a single report. Essentially just a simple concatenation. Eventually, there will be several reports grouped and the user will be able to render all of them for viewing online or saving as a single PDF.
I tried two sub-reports in a master report but it causes a lot of hard to diagnose page-break problems. I was wondering if there was a more straight forward option here. Thanks.
Combining all the report elements into one report would work, but the users also need to be able to view them as individual reports as well. To avoid having to maintain both an master report and multiple individual reports, you have a couple of options:
Create a master report and insert the individual reports as sub-reports. If you get page break issues, check the report page height and widths versus the subreport container height and width.
(If you have SQL Server 2008 R2 or later) Consider publishing your individual reports as a set of Report Parts. You can then reuse these in a master report.
I'm not a fan of subreports either, they work well in Crystal but are not really necessary in reporting services.
Why don't you just combine the reports into one? Copy all the tablixes / other objects from each report onto a new report. You can select all and copy and paste very easily, you just need to set up the parameters, datasets and data sources if they aren't shared.
You can set pagebreaks to occur after each tablix or a good trick is to use rectangles because they will let you control page breaks in their properties.
We are doing a conversion of Crystal Reports to SSRS. One thing we noticed was that the crystal viewer launches faster than ssrs. However, in crystal it buffers in the remaining data. To be clear, if I request 5 records run. The viewer launches in Crystal with recordset 1, however records 2-5 are not accessible till all supporting reads are complete.
In SSRS, nothing displays till records 1-5 are completly accessible to the viewer.
Giving the illusion that Crystal is faster than SSRS. In fact, I've done time tests same data same report. SSRS beats Crystal everytime in overall request completion. But Crystal displays information to the user more quickly.
Any settings or anything to mimic the behavior of Crystal on SSRS?
A little more digging revealed that the feature on the Crystal Webserver is 'page on demand' processing.
SSRS will try to do this automatically, but there are many things in the report definition that could prevent it.
I think the most likely culprits are sorting at the report level and page numbers. Move the sorts into your query, and take them out of your report definition. Otherwise, SSRS needs to retrieve all data to determine what the first row will be.
There are some nice tips on MSDN for this.