We try to run all our reports off stored procedures, however, now I am trying to report off a 3rd party server that I cannot deploy too. I am trying to find away to store the stored procedure on Server1, but execute on Server2 but the only link is the RDL which can see both data sets. I do not think this is possible.
Related
First time posting here, want to start by saying thanks to the community here for the amazing insights I've enjoyed over the years
I build reports with SSRS in VS2013 and currently have to paste/import MySQL statements every time I create/update the datasets. I want VS2013/SSRS to permanently refer to a local .SQL file instead of having me manually paste the query text every time I need to update it. How does I do this?
In my ideal world, I would have a folder bank full of SQL query files that VS would use to acquire data from the DB for the reports. Then all I would have to do is alter the separate, local SQL files and VS would take it from there.
I see 3 vectors for supplying the SQL query to the dataset: 1) Paste/Import the text query, 2) Table access, 3)Stored procedures. I thought there might be a way thru Stored Procedures but I'm not having any luck discovering if it's possible and how to code it from documentation and the web.
If it's useful, Visual Studio 2013 is platformed on a Windows server O/S.
Create your script as a stored procedure on the server you're querying. Configure all your reports based on that dataset to run that stored procedure. When you update the stored procedure, all reports that use that SP are affected by the code change.
I am not that much well versed in SQL Server. I am using SQL Server 2008 R2. I wanted to know if we can get the history of the text of the stored procedures?
I had modified a procedure on the server and now I want to get the previous text of that stored procedure? I know we can get the last modified date or history of the procedure when it was modified. Is there anyway to get the previous text of the procedure?
Any help is highly appreciated.
Unfortunately you cant recover it once you update your stored procedure. One thing to avoid this in the future is save your query before modifying it. SQL SERVER doesnt have a History Feature like JAVA.There are also third party tools which you can use if you want to connect your database to a source control.
Click Here
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.
Is it possible to call a MATLAB command within a stored Procedure?, something like
EXEC(MATLAB_COMMAND(Argument1,argument2))
Without any working experience concerning SQL Sever 2008, I would say no. Referring to the mysql documentation, a stored procedure is described as:
A stored routine is a set of SQL
statements that can be stored in the
server.
The idea is to store SQL queries on your SQL server.
You should proceed to other way round. Access your SQL Server from MATLAB, eventually calling stored procedures. All you need is a jdbc driver, leveraging MATLAB's Java scripting capabilities.
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.