I am configuring SSRS 2012 on my system. It gives an option to select/create a report server database. If I am selecting "choose an existing report server database" and selecting the database I am using for my application, I get an error "The database you selected is not a report server database...."
Why can't I use my existing database for reporting service? What are the correct steps to configure SSRS and using my existing database for creating reports?
The database SSRS is asking for is not the database where you have data for reports, but the database where SSRS configuration and temporary datas stays.
These are the default ones:
If you do not have those 2 databases, let the setup create them for you.
You will create Data Sources to your database when you will create your first report.
You can't pick your own database for a report server database, the database it is referring to is the one for the reportserver application itself.
So you need to first create a report server database and link your report server to that, then the report server application will work, then inside this application you create a data source which points to your database with your data you want to report on, you can then start writing your reports.
Have a look here for more detailed steps:
Install Reporting Services Native Mode Report Server (SSRS)
Related
I have a requirement to set up SSRS for reporting with one of our web applications.
Just now I have SSRS installed locally and pointing to the local version of the database for development purposes which is fine and works.
The live and test SQL databases are on Azure and I would like to be able to connect to them from the Report Designer locally to create the reports.
Does anyone have advice on how this should be done? For example, should I create a SQL database on Azure and use the SSRS configuration manager to set this as the reporting database, then from within the report designed connect to the live or test database when creating the reports?
thanks in advance
I'm trying to migrate a SQL Server 2016 database to SQL Azure via Data Migration Assistant. All the database tables are created, including the temporal ones, but only the temporal ones are missing data. Both main and history tables are completely empty.
Does anyone know if I have to do something special here to get this data filled in? Or do I unfortunately have to move this data over manually?
Specific to your scenario, if migration is the only concern, you can use SSMS to migrate the complete database with some easy steps. I tried it and there is no issue with the Temporal tables. All the temporal tables with data are migrating.
Follow the below steps:
Right click on the database you want to migrate. Select Task and from dropdown options select Deploy Database to Microsoft Azure SQL Database
Click on Next on pop-up window. On the very next window you will get options to connect your Azure SQL Server. Provide your Azure SQL server name, server credentials and click on Connect.
Provide the name for new database that will be creating in Azure SQL Server. Fill the Azure SQL Database settings as per your requirement. Click on Next.
Lastly, you will get a summary of all the settings you have done. Click on Finish to migrate the database.
Once your database migrated successfully, you will get summary with Operation Complete message. Click on Close. Your database has been migrated.
Check for the new database on Azure Portal and verify the data.
I'm trying to migrate SSRS report from SQL 2008r2 to SQL 2014 server. I used reportsync to transfer the report to the server. the reports are successfully transferred but however the roles subscriptions and datasources are not transferred. Is there is any way to copy or migrate the data sources, roles and subscription from one server to another without restoring the report server database?. Thanks.
I have used these migration tools which doesn't help me much.
i found the below link after a lot of struggle trying different things
https://azuresql.codeplex.com/releases/view/115207
https://msdn.microsoft.com/en-gb/library/dn531017.aspx#bkmk_how_to_use_the_script
better to test reports and subscription after migrate finish
In one of the ASP .Net site we are currently working we have a bulk load of SSRS reports. We have forms authentication for the site and reports have already been created and deployed in the report server. We are having so many problems with authentication when we set the report viewer control to access the server report.
I just want to know what are the advantages or disadvantages of using Local report vs Server Report
Thanks,
Raja
1- client report don't need to report server for rendering. (advantage)
2- you must make a server report by creating a report server project in BIDS but client reports must create in VS.
3- server reports use stored procedure or text script as data provider but client reports use dataset or xml datasource for this.
4- server reports use report server for rendering of the report but for client reports this work done at report viewer control.
5- client reports don't need SSRS installation but server reports need that.
6- for working with server reports you must deploy reports but in client reports you don't need this work.
7- for enterprise projects, it is better that you use server report but in other projects client reports are better.
Our reporting tool needs to access the database and get information from it. The tool uses Crystal Reports. The database can be one of SQL Server, Oracle, Sybase and Postgres. Currently, we install the database client with the report tool installation. We would like to avoid this client installation due to licensing issues and user privileges – we want non-admins to be able to install the tool as well.
Is there a way to access all of these databases without having to install their client software?
As I said, our tool uses Crystal Reports to generate reports, and Crystal connects to the database using OLE DB.
Where/how are you setting up the connection?
I created a basic Crystal viewer that attaches to data in SQL Server, Access and Oracle. The connection is embedded into each report at design time, using a specific Crystal Reports login on each server, to control permissions.
This allows the viewer to be installed for any user. The reports are developed by the Crystal team and stored centrally for anyone to use (assuming they have access to the report directory).