Is SSRS supported with Azure database? - reporting-services

We are planing to move our on premise database to Azure DB. We have SSRS reports as well. Is there any solution with Azure database for SSRS?

Unfortunately SSRS is not supported on Azure SQL Database. If you need SSRS it makes more sense to use a SQL VM on Azure or a SQL Server instance on-premises.
In this URL you will find deployment strategies for SSRS on Azure SQL VM.
You can deploy SSRS to a VM and use Azure SQL Database as the data source, but maybe is cheaper to have your databases on the same SQL VM.
Once you deploy the VM containing SSRS, you can then connect SSRS to an Azure SQL DB. This article discusses connecting Azure SQL Database to SSRS.
If you want to vote for SSRS to be offered as PaaS service please vote here. However, here Microsoft states is not planning to add SSRS to Azure SQL Database in the future.

Related

SQL Azure SaaS and licences for SSIS and SSRS?

When subscribing to the Azure SQL SaaS. Can I get access to SSIS and SSRS?
SSIS: Does a Azure SQL subscription allow me to build SSIS package on my local computer.
SSRS: Do I need another on-premises license to run a reporting server? As I understand, there is no SaaS version for SSRS, does this mean I will have to buy a full SQL server license for reporting?
Thank you in advance.
Microsoft's SaaS offering for BI and Reporting is Power BI. Which is adding support for traditional SSRS reports, and self-service data flows. See announcement here.
And if for all SQL Server development, you can always use the free SQL Server Developer Edition and SQL Server Data Tools on your local machine.
You need to have a VM to run SSRS which means you need IAAS. For SSIS you have Azure support using Integration Runtime means you would be using SSIS Catalog in Azure SQL Database.
When you procure a VM, you could always opt for VM with Sql Server installed else you could bring your own licensed version with you. Also there is the free Sql Server Developer edition available for solely personal usage. For SSIS, not really that you have to make the development in cloud - you would be using SSDT and then publish your packages to cloud.
Links - deploy & run ssis package in azure & procure Integration runtime

Migration of SSRS reports from 2008R2 to 2014 new environment

Hi I am having basic knowledge on SSRS and its been long time I worked on it. I am going to migrate SSRS 2008R2 reports to SSRS 2014 server.
So is that possible to transfer all existing reports without migrating database, connecting old database from SSRS reporting configuration service 2014?
If possible do I need to create new reportserver Database in the Old database because I am unable to connect to the existing reportserver database in the old DB from configuration services 2014?

SSRS Remote server access

An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'DSView'. (rsErrorOpeningConnection)
The feature: "The edition of Reporting Services that you are using requires that you use local SQL Server relational databases for report data sources and the report server database." is not supported in this edition of Reporting Services. (rsOperationNotSupported)
Hi, I have encountered the above mentioned error while doing an SSRS project. And from the research, it seems like it is SQL server related issue.
I am trying to access a remote SQL server....so I was wondering how can I get rid of that error?
Do I have to install SQL server Standard edition on my local machine or the server that I am trying to access should be installed with Sql Standard edition?
I have got Express editions installed on both my local machine and the server...
Thx
From Books Online:
Report data sources must be SQL Server relational databases that run
locally in SQL Server Express.
Features Supported by Reporting Services in SQL Server Express.
With SQL Server Express you can only use a Data Source where the database engine is from the same instance running SSRS.
If you need to connect to other instances your only options are to get a backup restored to your local instance or to install a SQL Server edition that allows remote Data Sources; most likely Developer for your own needs or Standard or above for any production instances.
It depends on what's allowed under your specific licencing agreement.
A neat way to get around this (that just worked for me) is to add a Linked Server on the Local machine to point to the server that hosts your remote data source.
Then modify your Dataset query in the SSRS report to look something like this...
select * from openquery(REMOTE_SERVER,'Put your original query here');

SQL Azure Reporting

For everyone playing with SQL Azure, what are you using for reporting? Do the Visual Studio reports connect seamlessly? What about reporting services?
Reporting Services will still connect and work as normal, BUT there is no SSRS service on the Azure platform. So it means that you will connect (most likely through ADO) from a different data centre (either your own or hosted SSRS) to SQL Azure, meaning that potentially a lot (too much) data has to come down the wire.
SSRS and SSAS for Azure are not officially on the Azure roadmap yet
My recommendation for a very fast, full featured reporting solution is Izenda Reports. It runs on SQL Azure and is designed for OEM integration with other Azure apps. It streams data from an Azure db or from an off-site db. Just give it a connection string and go.
SQL Azure Reporting was just announced at PDC10 (Oct 28, 2010) and a CTP should be available by the end of the year:
Link
We have at least one customer using ActiveReports with SQL Azure. Just connect with the normal SQL provider for ADO.NET or you can use unbound mode with ActiveReports.

SQL Reporting Services Express: datasource to external server

Using SSRS 2008 Express Edition, is it possible to create a datasource that connects to an external SQL server, or is it artificially limited to same SQL Server and instance of that Reporting Services engine?
I figured out myself. You can not define an external datasource.
See: MSDN
You could try using a linked server, where you would just call the procedures in the remote (linked) data source.