Is there a way to back up the subscriptions i have created on my reporting services server?
I store the reports in a source control and it would be nice to back up the subscription aswell incase something happens to the server and they are lost.
All SSRS data (reports, datasources, folder, security, subscriptions the lot) is stored in the ReportServer database. If you back this up, then you're OK.
Having your solution in source control is good too, but to recreate the SSRS set up is easier with a restore.
Saying that, the scheduling of subscriptions is via normal SQL Server jobs so you'll need msdb backed up too on the metadata SQL Server instance.
Related
I am trying to set up the scheduler for reports in SSRS.
I currently have read access to query the
database needed but I now need write permission to develop
and schedule reports according to this article.
What's the minimum database write permission that would allow me
to run and schedule reports in SSRS? I am using read
access just for using SSRS and not for any DBA work.
You don't need any database permissions to set up a schedule.
First, your SSRS reports live in the Report Server database specified in the Reporting Services Configuration Manager. If SSRS did not have write access to it's own Report Server database, you would not be able to create reports or any other content.
You are probably accessing another database with customer data with read only access. You do not need write access to this database to create schedules.
SSRS accesses the report server database via the account configured as a Service Account in the Reporting Services Configuration Manager.
You will have to have your user granted the necessary permissions in SSRS in order to create and modify schedules. You can configure that by clicking the gear at the top right. If you are in the Administrators group on the local machine you will have full admin rights to the SSRS portal (that is the BUILTIN\Administrators role and it will override any permissions set in SSRS).
Schedules execute via the SQL Server Agent on the SSRS SQL Server. Your service account should be able to create and execute jobs via SQL Server Agent.
If all of this is set up right and you're getting a specific error trying to create schedules, I encourage you to post that information.
Let me first describe the actual situation: We want to build a new SQL Server enviroment based on SQL Server 2016. AS you may know, in SQL Server 2016 the mobile reports from Datazen are integrated. So far so good. The Problem: In our current Enviroment, there is one internal Datazen Server and one external server. The external Datazen server exists only to read data from the internal one. So there is no direct Data Access (to Data Sources), the administration part is disabled and only the needed Services (to read from internal server) are installed. We want to build that same archtiecture in SQL Server 2016 Reporting Services. Do you know any way to do that?
I thought the best solution was a second SQL Server with Reporting Services but only read access on the other SQL Server (didn't found any setting like this).
We don't want the internal server to be accessible over the web beacause of security.
interesting question, but not sure i understand correctly ;) what do you mean with "the external datazen Server exists only to read data from the internal one"? How does this configuration look like? Do you have a sale out Deployment where the external Servers hosts "Web Application" and "Share Cache Instance" while internal Server hosts "Data Acquisition" and the same roles as the external Server?
In SSRS you can also Scale out web frontends, but all Servers will act as "data acquisition server" to stay in datazen terminology. Do you have security concerns with this topology? Whats the difference to have the data "read only" in DMZ or connect from DMZ/external Server to internal datasources? One Option would be to do a secure Application Publishing of internal SSRS Server with a Firewall like Microsoft ISA Server
We are planning to deploy reporting service using Microsoft Reporting Server 2012. As I understand it, there will be three components;
Database (SQL Server)
SSRS (Reporting Server)
IIS (Web front end) - SharePoint (alternate Front end)
In setting up the Proof-of-Concept, the dev installed SSRS and SQL Server on same box (let's call it the DB server) and is redirecting client browser to a URL on DB Server from web front end.
Is it possible to architect the solution so that the web front end is the only destination for client browsers, SSRS lives on its own dedicated server separate from both the Web server and the DB Server?
How will authentication work in this scenario? We are using integrated authentication using Enterprise AD.
Configurations I have used in the past are these:
SQL Server on one server; SSRS native on another server. Users accessed reports via the SSRS Report Manager web UI that comes with SSRS.
SQL Server on one server; SSRS install in SharePoint Hosting mode on another server. Users accessed reports via SharePoint.
I am not 100% sure what you mean by “web front end is the only destination for client browsers”. If you mean that the end user only hits a web server, and not the database server to get reports, then either one of the above will work. If you have an existing intranet site that you want to host reports in, you can do so via web parts, if you are using MS technologies. You will still need SSRS setup somewhere so you can deploy reports, and the web part would read from it. Or, you can continue the redirect to either Report Manager or SharePoint if you go that route.
As far as authentication: the authentication between SSRS and SQL Server is usually done via an AD (Active Directory) user/service account that SSRS runs under, and also has access to the databases is uses on the SQL Server.
The authentication that allows users to browse and execute reports is usually done via AD as well. You can add all users to a central AD group and give that group Browser permissions on the SSRS server. This authentication would still apply if you use web parts to host reports outside of SSRS Report Manager.
The authentication that SSRS uses to pull the data that ends up showing in reports is usually SQL Server authentication, or whatever authentication that your data source supports where you can send a user name and password (which is stored within a shares data source on SSRS).
More Info
I've created a Crystal Report project with MS Access DB backend on our development server in 1st. Step. The path is smth. like H:...\db\my.db. After compiling the project, I've deployed it on another Server and start it over mstsc.exe to open a remote session on it.It functions.
In step 2 I inserted a subreport with a data source in the same db and linked it with the main report over id field. Checked it on development server and copied to production one. Now, when I try to stat the report I'm prompted to log in and the Server and Db name are shown to be ones from development server.
Is there any way to set all reports data sources and links programmatically at the runtime?
Can you use integrated security? Or did you want the connection's userID and password stored with the report?
We have a analysis services olap cube (SSAS 2008) deployed at a test server (MS Serve 2008) in our domain, you can browse the olap cube via ssms without problem. No problems with olap cube itself so far. The user account is admin on the analysis services server.
We also have reporting services (SSRS 2008) installed at the same test server and have a datasource inside the reporting services report that fetch data from the analysis service olap cube. We have set up windows integrated authentication setting but the user trying to connect trough reporting services report to the olap cube get access denied.
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'DsMillCd'. (rsErrorExecutingCommand)
Either the user, KORSNET\TFMAN, does not have access to the AnalysisServices database, or the database does not exist.
If i try out the same olap cube and report trough business intelligence studio local its working, so it must be some setting on the reporting services server.
Do reporting services connect to the analysis services as a another domain account?
I have searched and googled for a answer for about 6 hours now without luck, i'm getting a bit frustrated to get this working.
I think its only a configuration setting that i have missed, so all suggestions are welcome...
Are you logged on as KORSNET\TFMAN?
If the datasource set up for the report is set to use the credentials of the user then it will attempt to authenticate to the database as that user.
Does IE show the site as being part of the local intranet? If not go into security settings and add it.
Does that user actually have permissions to read the database?
It could be the "double-hop" problem where credentials can be carried and used once, but not again, however I think this is unlikely in this situation.