I have created a very simple report in Visual Studio (also tried it in Report Builder) that just returns 10 rows from a table in a MySQL (Not MSSQL) database. I changed the background and foreground color to make sure I could clearly see the rows in the report.
There are no parameters and it does not use a stored procedure. It's a straightforward SQL query:
select TASK_INSTANCE_ID, TASK_NAME, ASSIGNED_NAME, CREATED_DTTM
from task_instance where created_dttm > date_sub(now(), interval 1 day)
limit 10
Here's the result when previewing the report in Visual Studio. You can see that it is showing 10 rows of data.
I then publish that report to our SSRS server:
And when I view that report on the SSRS server I get 10 blank rows.
To confirm that I was actually seeing the rows and they were just blank, I changed the query to return just 5 rows. This shows that there are now only 5 blank rows, but with the defined background color.
For reference, I also created a simple report from an Oracle DB and published it to the same folder on the same SSRS server. This report works just fine.
So it appears to be something related to using a MySQL DB, but I have not been able to find anything that explains what I'm doing wrong. Any pointers/help will be greatly appreciated.
I then tried to add a couple new columns to the SQL query.
I used the ROW_NUMBER function to get the rownum of each returned row
I added a dummy column with a constant value for each row
Works fine in the Query Designer:
Works fine in the Preview:
Shows the new columns when published to SSRS, but still shows blank cells for the other columns:
If your problem is/was the same as mine then I think you will find that if you export your report to excel from the report-portal that all of the data that you expect to see is in fact present.
After some digging into the report properties and trying page width settings etc. I found that I had different values for the CanGrow property of the cells in the row and once I set them all to be the same -- True in my case -- then the report rendered as expected.
I am thinking that the reason that Excel showed the data is because it effectively ignores the CanGrow setting so having a mixture of them didn't matter.
I hope that this helps -- you or others who encounter it later -- as it was a really bizarre thing to encounter...
Related
I'm having an issue with report preview in Reporting services.
Blank data being displayed in Report preview only for few rows which have a length greater than 38( the data type for the field is Varchar(60)).) But in SQL Server able to see the data. Even the Query designer in the data set also displays the expected data. When I preview the report, then, for few rows it is displaying the blank value. I tried refreshing the data set/ adding a new field (given a new name) and used the source field for this new field/Changed font size /added new tablix and tried out/added new data set and tried out. But nothing worked out. Still, it is displaying blank data for a few rows. Can anyone pls. help with getting out of this issue?
Thanks, #BJones & #Alan Schofield for trying it out. I found the solution for this. Actually, in server1 the value is blank and in the server2 the values are set up. The report runs based on the server1. So, only it was displaying the blank data. Actually, there are no issues with the report design or logic. It fully depends on the environment it runs on. Anyhow the issues solved now. I'm happy for that.
I have a report, that used to have columns in the following order [A,B,C,D,Banana,E]. I was then asked to make some changes to my report, which I did so that the report columns now has an order of [A,Rocket Ship,Banana,B,C,D,E].
When I look in Visual Studio or look at the report on SSRS, I see the correct order, HOWEVER, when I let the subscription run, I see that it is still putting out reports with the wrong columns. Has anyone else seen this phenomenon? I've tried creating a brand new subscription, but I still get the old Column order.
Any help is greatly appreciated.
Check to see if the report using any caching or snapshots.
It might be using an old copy - though I would think it would be the same as one rendered manually from Report Server.
The issue is that the CSV report that is created isn't dependent on the report that is created with SSRS. Essentially, it just spits out the results of the SQL query into a CSV file.
I have a bear of a problem here. The user wants a report that shows the earnings, deductions and liabilities (EDL) code of each employee or null/blank if an EDL code doesn't apply to that employee. I needed one row for each employee name and columns for each possible EDL code combination. I got that answer fixed from my previous question here:
Struggling with a dynamic pivot on multiple columns with one being concatenated
I ran into a problem where there are a potential 270 column headings (EDL code combination with "subj", "elig" or "amt" appended) but not every employee will have a value for every column and security settings lock me out of seeing 1 of the 3 payroll groups. This made my report very limited in that when I ran it I could only show on the Crystal Report the data for what columns I had at the time I created the Crystal Report. Well, the user who requested this report has access to payroll group 1 and if even one of those employees had an EDL code that I didn't have in my data when I created the Crystal Reports file then the report wasn't useful to the user. We figured a way for her to get the info she needed by her logging into SQL Server and executing the stored procedure and she did what she needed to do with the data.
Fast forwarding to today I have to create this as a report in SSRS or give detailed instructions on how she can do this in the future if need be since my contract is coming to an end. I'm not familiar with SSRS but I thought maybe that would meet her needs over Crystal Reports. However, I'm running into the same problem. When I add the stored procedure as a dataset (adding it in as text to execute, not clicking the stored procedure radio button) I only see the EDL codes from that particular query not all potential combinations. I need a way to maybe dynamically add columns to the SSRS report, does such a thing exist?
Issue I get for one of my shared data sets only on certain parameters. If the parameter returns nothing for that dataset then I seem to come across this problem, there is a tablix in this report that uses the shared dataset and if I remove the tablix but keep the shared dataset I still get the error on the report preview.
The dataset uses a MDX query (SSAS) to get its data, if I run the query from the query designer it returns 2 rows but the dates in the rows are outwith the scope of my report so the report would return 0 and I assume thats my issue.
Anyone got any ideas/tips?
Uses SQL Server 2008 R2
Thanks
Managed to get round this issue by having an embedded data set rather than a shared one.
Gets around the issue, very annoying though!
I have a report working well where I extract the number of logins per user. Each login takes up one row on the report.
I have date parameters and my DB goes back a year. However it seems the report will only show 40/50 rows despite a report expecting to deliver, say, 250 for the amount of times I logged in.
Is there some setting in reporting services that limits the number of rows delivered. Can't find it anywhere..
Thanks.
The answer to your question: nope, as far as I know there's no real equivalent of SQL's TOP 50 statement in SSRS itself.
Some things that come to mind that may be causing your symptoms / can be investigated:
What happens if you run the query for the dataset in SSMS? Be sure to fill in the exact parameters the report's using (if any).
Run the query as a test from SSRS designer. If you're using Visual Studio: right-click the dataset and hit "Query...", then hit the red exclamation mark and fill in any parameters if needed.
Try putting a CountDistinct call (on your dataset) in a textbox somehwere in the report, by itself.
Check the filtering and grouping on your tablixes, perhaps even by looking at the XML source code for the RDL.
Show the parameters in textboxes (oldskool printf debugging! :D) to make sure they're what you expect them to be when the report's run on the Report Server. If they're not: try deleting the report on the server and re-deploying it.
Have a look at the ExecutionLog2 View in the ReportServer database, specifically the Number of Rows returned.
As mentioned in the comments by Atilla: You may also monitor exact SQL SSRS sends to server using SQL Server Profiler.