We have a reporting server which has a bunch of reports and some ad hoc user reports created by users using report builder. Now we need to move all these to a different server. The new server already has some reports in it. I need to move all the reports from the older server to a folder in the new server because of this moving the database from the old server to the new server is not an option. I want to know if we have some other way to export all the reports from the older server and then deploy it to the new server.
You can use the ReportingService web service to programmatically interact with SSRS. I used it once to create a basic bulk report uploader.
http://msdn.microsoft.com/en-us/library/reportservice2005.reportingservice2005.aspx
Alternatively, some googling turned up this application, although I've never used it.
http://www.sqldbatips.com/showarticle.asp?ID=62
Related
Our team has setup a Windows Server to specifically run SSRS in it. We have the reports running well but we wanted to manage several tasks under the Browser role to get rid of a couple of things. I believe this can be accessed through SSMS by logging in to the Report Server. I did this just fine but when I'm trying to open the properties of the Browser role, it is grayed out and can't be selected. Am I doing something wrong here?
A couple of notes to clear things out:
I'm already using an admin account on the server
The Reporting Server is installed separately to a source DB from which we get to access data
I'm able to do this just fine when both Reporting Server and source DB are on the server
I'm using SQL Server 2016 with the same version of SSRS
We have figured it out. We just need to open SSMS as administrator. Might just be a user error of some sort as we do not need to do this on other servers. Thanks.
I want certain reports to execute as a super user, but when I change the Credentials section for the .rdl embedded Data Sources, these changes do not propagate through to the web server. That is, users still have to enter their username/password on the web server, and run into permissions issues.
The current workaround is to "Manage" the report on the web server (using the ellipses...) and telling each report to log into the data source "Using the following credentials..." and putting the super user creds.
But this means that everytime we redeploy the report, we need to do this. We would prefer if the settings we have in the actual .rdl in SSRS actually show up on the web server after deployment.
I suggest to use shared datasources for your reports. For each database a report needs access to, create one such shared datasource. The default project settings for Report Server projects in Visual Studio is to not overwrite datasources that already exist on the server when deploying the project. This way, you will have to set the credentials in the Web Portal for each datasource only once, and you don't have to care about that when deploying updated reports.
I'm trying to deploy an SSRS report to a remote server (that is not on my network). I'm not sure how to do this. For a machine on my network, I would just change the TargetURL, but I'm guessing there should be somewhere that I can associate credentials to deploy to a remote server, but I'm not finding it.
I know this is an old post but if someone is wondering about the same question.
I am using vs2017 enterprise. So when you configure your remote url and folder name and everything is perfect to build your project, you hit F5 or deploy your project. Upon successful building vs will prompt you for your report servers credential. Then you do the usual and vs will do its own job. In a moment you will be able to access your report.
Just read about the permission requirements before you try it.
Hope it will help someone.
Thanks
I face a similar issue delivering reports to various servers (customers and dev,qa,staging and production.) In visual studio the best way to do it is start a new project for the new server and import the new reports into it. You end up with a new project for each server.
I found TFS / VS unwieldy and my workflow to manage it unfortunately is doing it manually, or using one of a few open source report uploading tools (there are powershell scripts to do it but I find the tools are more user friendly.)
Best thing to start with is doing it manually; which will sort your initial problem.
Save the file out of your report writer to disk.
In Internet Explorer log into the Report Manager of the remote server http(s)://remoteservername/reports and navigate to the folder you want. Then upload the report.
When its uploaded you may need to fix the connection to the database.
Once you get used to doing this you can use a tool like reportsync to easily and quickly move reports between servers.
I have report solution file with one project and one report.I have designed rdl report using BI in SSDT tools. After creating report successfully build is success and preview is ok. No problem did not arise when i did create report.
Now, I want to deploy this report to my remote reporting server. I gave a url like this www.plumeria.arvixe.com/Reports into Target server url. when i press deploy then need username and password, i gave that. after certain time it appears a errors like this.
Many times i have tried but not get a proper solution step by step deploy rdl report to remote server.
Is there any solution? Thanks.
"like this www.plumeria.arvixe.com/Reports into Target server url" is not correct. What you are referring to is the Report Manager.
You have to correctly specify:
Target Dataset folder
Target Data Source Folder
Target Report Folder -->From your project
Target Server URL-->Get it from Reporting Services Configuration Manager
Target Server version.
You may need elevvated permissions in SSDT.
My target url used in my book is as follows:
http://HODENTEKWIN7/Report_Server_Kailua
The instance name of SQL Server is Kailua and it is native mode.
This is a comprehensive book covering SQL Server 2012 both native mode and SharePoint
So my problem is that on an already working instance of SQL Server 2008R2, a former colleague of mine installed a new instance, apparently with the same name and leaving us now with an empty Report Manager. The URL for the old one still works, but it only shows me the file structure for the old Report Manager.
Is there a way to somehow extract the old RDLs (considering it has no graphical interface anymore) so that I may load them to the new one? Or alternatively, set the ReportServer service to use the old instance in order to download the RDL files?
Thanks in advance.
I can think about a couple of options:
Download through Report Builder
It sounds like the old ReportServer URL is available? That's something, at least.
One option that might have the least impact is connecting to the old ReportServer through Report Builder, opening the RDL files then saving them to the location of your choice.
Connect to the ReportServer:
Navigate and open the file you need.
Click Save As to save the RDL as required.
Start/restart different instances
Based on your description, it sounds like both instances are trying to register the same URL.
If possible, I would stop both instances, then restart the old instance which has the RDL files you want.
Hopefully this will allow the old instance to register its URLs successfully and allow you to connect to the old Report Manager URL and download the RDL files.
You can check the different URLs each instance is using through the Reporting Services Configuration Manager application: