I am using a simple table object in SSRS that uses the default format of Arial 10. It shows correctly in design mode, but when I execute the report, there are different fonts in different columns. Notice in samples below, during report execution, columns 1,2 and 5 are different than columns 3,5. Can someone explain this or point me in the right direction to get consistent output? Thanks!
Design Mode
Executed Report
Did you make any changes in the format?
if so, you have to clear cache by deleting the
file "reoprtName.rdl.data" in the project folder,
or rebuild the report.
Related
I've returned to our reports collection after a couple of years away, and added a new report which has a simple tablix containing a few columns, but many rows from the dataset.
The problem is, the report (in Preview in VS, and when run on the Report Server) only shows some of the rows returned by the dataset, and doesn't enable the page navigation icons in order to scroll through the data to access the rest.
Where do I find the settings which control these things, please?
UPDATE:
Looking at some pre-existing reports, it seem that these exhibit the same problem - it would appear that SSRS can only display about 5,000 rows regardless of how many the dataset contains.
There is a 'hidden' setting in the XML code (not available via the UI AFAIK) called InteractiveHeight. Removing this line resulted in the paging starting to work
I have a report containing 6 charts each displaying some percentages over an interval of time.
I have put all the 6 charts in a separate RDL file and using it as a sub-report in my main report which also contains a matrix.
The issue I am facing is the chart becomes too slow (>10 s of rendering) as soon as I implement the drill down functionality. Without drill down its about 1 s.
The drill down report parameters do not have any functions - I have already converted all of them to either fields or parameters.
Its not that big of an issue yet - but we have some major changes coming to the report which may increase the number of charts to about 15 - and all of them will contain drill down action. Once that's implemented the report will definitely take more than 30 s which would not be acceptable.
Any pointers would certainly help.
Thanks.
Drill downs can add a huge amount of output to a report, depending on the number and complexity of them. I've seen that each drill down in our reports adds about 2K to the size of the rendered report. Depending on how you added the drill down to the chart, every single point could be a separate link, and these add up fast.
Run the report without drill downs, and export it to .MHTML.
Run the report with the drill downs, and export it to .MHTML.
Compare the size of the outputs.
The reason for .MHTML output is that one file contains everything. The file sizes should help you do the arithmetic with regards to the number of drill in your reports and help you reduce it to an appropriate amount.
I have a stepped report that has 5 row groups. Each one uses an expression as the value to group on. The user selects a value for up to 5 different parameters and based on those parameters is how the report is grouped.
With certain combinations of parameters the report may take 2min + to run in the preview pane in Visual Studio. When I deploy the report to the SSRS server the same combinations of parameters runs in 10 seconds or less. Out of curiosity, I created a copy of the report and removed the expressions from each of the row groups and specified a field to group on. In that case it previews just as fast as when viewed on the server.
Anyone have any idea what may be going on here?
I'm currently using Visual Studio Enterprise Update 3.
I realize this is an older issue, but maybe this will be some help to you.
I am experiencing similar symptoms to what you have described and it comes down to using dynamic fields in grouping statements. Apparently, any other statement can use dynamic fields without issue, but groupings incur a huge performance hit.
This link outlines the symptoms and causes.
I don't know if it was in that particular link or not but I read something about how the ReportViewer control when it renders to HTML has a bug in it that only happens when the control is running under .Net 4.0 or higher. In .Net 3.5 the performance is pretty much the same as it is if you were to run the RDL in the Report Viewer application.
If you are able to do so, the quickest way to get the report viewer component to work is to have the application pool IIS is using to run under .Net 2.0 (or 3.5 if that option is there, since they're basically the same thing).
If your application uses .Net 4.0 or higher for other functionality, there isn't much I've been able to figure out, short of rewriting the report to remove dynamic references from groupings, but that significantly reduces the interactivity of the report (no expand/collapse options in table rows/columns).
For reference, I had a report, where the query took about 2 minutes to execute, and then rendered almost instantly afterwards if I loaded the RDL in SSRS. That same report rendered using the ReportViewer control in .Net 2.0 took about 2 min 30 sec to fully render. Using the exact same code, but changing the app pool to use .Net 4.0, the report has been "rendering" for roughly 15 minutes now and still hasn't come back.
First of all and a bit obvious, if you are running your report in a development machine it won't have the same computing power as a server. Even if you are running VS from the server it won't run as fast as a deployed report.
The cause -as you may notice- for the slow performance is the grouping expression. It seems your report is taking to long to process so check this article from a Technet post. I copied and pasted a paragraph below:
Many levels of nested and adjacent groups in a Tablix data region can
affect report processing performance. Consider both the level of
grouping, the number of group instances, and the use of aggregate
functions which require evaluating after group, filter, and sort
expressions are applied.
I recommend you try to perform the grouping in the datasource at SQL level, you can also pass parameters to the query to set the desired grouping there.
Let me know if this helps.
I have a tabular model that I've processed and deployed.
I'm having a problem getting SSRS to reflect the newly deployed information. I have a shared Dataset accessing a shared Data Source. When I run the MDX in the query designer of the Dataset, the correct numbers are returned. When I run the report, however, the old numbers still show. I've tried deleting the .DATA file but it didn't help.
EDIT:
I've verified that the problem is in the SSAS database itself. I queried it with drillthrough from SSMS and saw that it is returning rows that aren't in the source views any more. They used to be, but no longer.
This almost seems to be some crazy caching issue. I've rebooted and dropped/redeployed the SSAS database and no luck.
Any thoughts?
I would suggest a few steps.
Ensure you are connecting to the correct tabular model.
Expand the tables in the tabular model, and right click one of the tables and click "Process". Check all the additional tables in the model.
Change "Process Default" to "Process Full" (Process default does not always work correctly)
Click Ok.
You should now see the model process table by table.
I would close and re-open the report.
Actually I would completely ignore the BIDS / Visual Studio Preview pane as it is riddled with bugs and inconsistencies and proves nothing (assuming your end users aren't using Visual Studio).
Instead I would deploy the report for each test run to a test environment / folder on the host server (Report Manager / SharePoint). As well as being a realistic and meaningful test, this has many advantages such as being able to leave multiple IE tabs open with various parameter combinations set, then just refresh them after a Deploy to retest.
I have used a 'Union' to combine two reports showing different dates. When I open the report on it's own it works fine with the two dates shown. However when I drill to the (union) report from another on the dashboard it only shows one date. Is there a dashboard filter that I may need to un apply or is there some other explanation!? I cannot seem to get the report to function as required from the drill.
Tough to answer - need more info. Some possibilities:
You're not really drilling to the report you think you are. You can learn a lot by looking at the log to see what's happening in the target report.
You may be passing values from the first report that exclude the date in the second report. Check your filters in the target report. Look at the generated WHERE clause in the log. Run the SQL directly against the database. Is the date still excluded?
You want to start by checking the physical SQL which is written to the nqquery.log. It can also be obtained by viewing the log in Answers directly. Another way is to go to Administration > Issue SQL, enable presentation server cache, set the debug level to 7, execute the SQL and click on the view log link. The Physical SQl can also be tested against the actual database, if that is where your data is coming from. Examining both - your Logical SQL and your Physical SQL can resolve a lot of minor issues, including this one.