We're considering using the VS 2010 Microsoft Report Viewer in Remote mode. My question has to do with is where data retrieval takes place. Let me give an example. Say we have a report with two parameters. These parameters are then passed as stored procedure parameters when data is retrieved. So, my question is, when is the stored procedure called? Is it called from the SSRS 2008 server and then the data and report sent to the report viewer client or, is the stored procedure called from the report viewer client? Secondly, let's say the report is being displayed in the report viewer client, and the user changes the parameter values and refreshes the report. Is the stored proc called from the client or is the stored proc somehow called from the server?
In remote mode, all the report processing is carried out by the remote SSRS server - in your example, the stored procedure would be executed on the server and the report/data returned to the client.
If the parameters are changed and the report re-run in this scenario, a new report execution request is submitted from the client to the server, processed at the server and report/data returned to the client in the same way.
Related
We have developed some paginated reports using Procedures from Azure SQL Database. Reports are showing correct data when executed in Report Builder, the problem starts when the same report is published to Power BI app (Web). The values are doubling sometimes or values showed as nulls sometimes. There is consistency of data in each refresh of the report. Parameters are passed in the URL directly
Thanks
scmy
I developed a report using the getdaye() function in the query. The report runs fine on SQL management Studio.
I created a report using the SQL server data tool and the report is based on the query that I wrote in SQL studio. I have established a connection using the data source and am able to connect to the SQL database. When I run the report using the tool after a couple of days the report data is different from the data that I get when I run the query using SQL management studio. Obviously the Getdate() is not fetching the right date.
The report data maches only when I copy and paste the query in the SQL server data tool and then run the report.
Am I doing anything wrong or should I use create a parameter for the date and direct the default values = Now() on the sql server data tool.
Is there any other work around for this.
Hem
I guess that did not publish the report to a Report Server but repeat to preview the result in Visual Studio (SSDT). SSDT caches data to improve the experience in SSDT and retrieves data from the database only when needed. "Needed" means that you either change the query or choose different parameters. You could of course pass a parameter to the database server, but if you don't want that, you will have to clear the cache from time to time. Look into the folder where the report is saved and delete the *.data file with the same name as the report. You can make this task very easy by adding a menu command to the tools menu as described here.
Please Help
I'm using SQL Server 2008 R2 and SSRS to develop a report. I've created a stored procedure on the server and I am accessing it through the report. Within SSMS, the stored procedure runs and returns data just fine. Also, within Visual Studio I run the debug version of the report and it outputs data just fine.
The problem arises when I deploy the report and try to run it in the web portal. It runs without any errors and displays the report header, but there is no data in 2 columns out of 7 ! I've tried creating a new report accessing the same stored procedure and the same thing happens. What could cause this?
A few possibilities;
The SPROC does not returns this data now and the report is only working in design view because it is using cached data (you can verify this by deleting the .data files in the report file directory and seeing if it stops working in design view)
You have a Shared Datasource configured which points to a different server/database on the report server than it does in Visual Studio, in that other server/database the sproc doesn't have data for those columns
have a strange one. We are running Sql Server 11.0.3000. The report is giving an error
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'Audit_Detail'. (rsErrorExecutingCommand)
Invalid object name 'dbAudit.tblRangeReport'.
The thing is, the report uses 3 stored procs to go after data in a database called dbSalarySurvey. The three sp's do not mention the dbAudit.tblRangeReport. There are no functions or views in the 3 sp's that access that table. Further more, if i run the report in VS 2012 the report runs. If i run profiler on the dbAudit table when VS runs the report, the report does not query the dbAudit table. Only when running the report from the web browser do i get this error. This more detailed version of the error come from running the report on the Sql Server REporting services computer.
I have tried restarting the reporting services service. We have also deleted this one report from the reporting services server and republished it. Have also tried to republish the dataset. Other reports in this project that use the datasource and the same tables run.
Anyway, was wondering if anyone had any sugguestions.
Thanks
shannon
It's fixed. it was a pebkak error in the stored proc. It's really strange though. Honest to goodness, the proc was running in my dev env but not when running from a browser. I had already checked profiler like was suggested below and done the xml scan too. In the end.. just missed it i guess.
You need to trace the SQL to determine.
Are you connecting to the right database?
Are the procs you expecting to see, the ones actually being run?
The procs you are running are correct?
Open SQL Server Profiler
Start New Trace
Click Event Selection, Select the following events
Click - Show All columns
Go into Column Filters
and filter on your DB, and possibly even your login name (the login name of the SSRS server)
Once you've done that, call your report and look to make sure all the procs are called that you expect. Track issues from there.
I created a report in SSRS, and deployed it. I went to the properties of the report the Process option, and tried to set up Cache a temporary copy of the report and got an error 'Credentials used to run this report are not stored.' I get the same error if I go to Snapshot Options and try to select any of the options there.
Thanks in advance
As per the error, you need to set up the report Data Source similar to the following:
If you're not storing credentials you cannot cache reports or create snapshots.
With cached reports, a temporary copy is created when a user runs a report and this can be used for subsequent runs of the report. Since this could be performed by different users, the only way this can work is if the same connection is used to the Data Source each time; it must be independent of whoever is running the report when the copy is cached.
Same principle for snapshots; no guarantee who will run reports based off the snapshot, so the Data Source connection must be independent of the user running the report, i.e. stored at the Data Source level.