i have a sql server 2014 and few databases in it,
Can i setup and install ssrs 2016 and use the databases on sql server 2014 for making few reports?
The reason for thinking so is just found that ssrs 2016 report rendering engine have some advantages like it follows html5 rendering standards
So can some one guide on this
Yes, you can use SQL Server 2014 database as either a host for the report server catalog AND/OR as a source for report data. They are cross compatible back to SQL 2008 for hosting and forever for data.
Related
We are processing to migrate SQL Server databases from 2008 to 2016.
We are searching now for expired function or utilities used in SQL Server 2008 and not available in SQL Server 2016 before migration.
Do you have reference for that?
Here are few features removed in SQL Server 2016 (from MSDN):
SQL Server 2016 is a 64-bit application. 32-bit installation is discontinued, though some elements run as 32-bit components
Compatibility level 90 is discontinued. For more information, see ALTER DATABASE Compatibility Level (Transact-SQL).
Though you are migrating from SQL Server 2008 directly to SQL Server 2016, you need to consider the removed features of SQL Server 2012 & SQL Server 2014 as well
Discontinued Database Engine Functionality in SQL Server 2014
Discontinued Database Engine Functionality in SQL Server 2012
I have a server running SQL Server 2014, Enterprise Edition, with many large databases. I am currently using SSRS 2014 to create on-premises reports from this data.
I really like the new features of SSRS 2016. My question is: can I install SQL Server Express 2016 (for free) on the same server, just to utilize the new 2016 SSRS, while my data remains in the SQL Server 2014 databases?
I don't think you can use express to read data from any of the "higher" edition SQL Servers (like enterprise or standard), which I would assume that is what you're planning to do.
Otherwise you could install as many SSRS servers you would like for free. See Features Supported by the Editions of SQL Server 2016
I am setting up a new SQL Server 2014 Enterprise Reporting Services instance on a Windows Server 2012 R2 server.
In Reporting Services Configuration Manager, when I select the SQL Server instance where I want to setup a new report database, the error message below is shown:
The feature: "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services.
Error:
The SQL Server instance where I intend to setup the report database runs SQL Server 2014 Developer Edition build 12.0.4422 (which is displayed in Management Studio and ##version) and the SQL Server instance where I am configuring Reporting Services runs also MSQL 2014 build 12.0.4422 as displayed in Reporting Services Configuration Management - but Enterprise Edition (I've just installed SQL Server Cumulative Update 2 from https://support.microsoft.com/en-us/kb/3075950).
If I select an instance which runs SQL Server 2008 R2 Enterprise Edition build 10.50.4260 instead, the error is not shown and the setup proceeds correctly - but unfortunately this is not the instance where the report database should be.
What am I missing here? How can I solve this issue?
Thanks in advance,
Cristhian.
This behavior is correct. The reporting services database is supported on a wide range of versions.
You are not allowed to use a production reporting services against a developer version database. (Why would you want to!). You can either use a developer edition of reporting services, or an enterprise database.
I'm planning to migrate all the SSRS reports from 2008R2 server to new sql server 2014 environment. As far as migration is concerned, I was asked to take the backup of 2008R2 report server database and restore it in 2014 server.
I was not convinced with this since there may be new tables available in 2014 Report server.
The new features of 2014 cant be utilized if the old report server database is restored.
Please let me know if this thought is correct.
Are there any new tables available in 2014 report server database?
What is the best option to migrate ssrs reports from 2008 r2 to 2014 server?.
Your question is a bit confusing, I will assume you want to move the database from a Server A with SQL Server 2008R2 + SSRS 2008R2 to a Server B with SQL Server 2014 + SSRS 2014.
Are there any new tables available in 2014 report server database?
There is no official communication on it.
If you really want to know it you could do a schema compare between the 2 versions.
But do not forget to compare everything, not only tables:
Columns
Stored Procedures, Functions
...
Database structure is not the only thing to take into account, what about:
All the configuration files
Encryption Keys
...
What is the best option to migrate ssrs reports from 2008 r2 to 2014
server?.
Short answer:
My recommended way of doing it would be to use RS Scripter and generate a script on Server A with all the objects (reports, datasources, subscriptions, ...) you want to move.
Then you can restore it on Server B.
Long answer:
If you really want to migrate the full database like you were asked to do, there is no officially supported way to move the database to another SQL instance and upgrade the version at the same time.
You could try to follow the steps to Backup and Restore Operations for Reporting Services, and apply it to a newer SQL Server instance with another SSRS version, but it will be at your own risk.
The supported ways to do would be to either:
Upgrade from SSRS 2008R2 to SSRS 2014 on Server A
Move from Server A to Server B
or
Move from Server A to Server B
Upgrade from SSRS 2008R2 to SSRS 2014 on Server B
Here are the related MSDN articles for these operations:
Migrate a Reporting Services Installation (Native Mode)
Upgrade to SQL Server 2014
Again, I would advise using a tool to migrate the reports and other items instead of trying to migrate the full database.
I do not think restore 2008R2 reportserver db on 2014 will work, because the report definition schema is totally different.
I did a migration task to move 2008R2 reports to 2012. Because there are hundreds of reports on the 2008R2 server, I found the easiest way is to write some codes to read report definition, and then create on 2012 server.
From: https://msdn.microsoft.com/en-us/library/ms143747.aspx
There are two general approaches to upgrading a Reporting Services
deployment:
Upgrade: You upgrade the Reporting Services components on
the servers and instances where they are currently installed. This is
commonly called an “in place” upgrade. In-place upgrade is not
supported from one mode of Reporting Services server to another. For
example, you cannot upgrade a Native Mode report server to a
SharePoint mode report server. You can migrate your report items from
one mode to another. For more information, see the ‘Native to
SharePoint Migration’ section later in this document.
Migrate: You
install and configure a new SharePoint environment, copy your report
items and resources to the new environment, and configure the new
environment to use existing content. A lower level form of migration
is to copy the Reporting Services databases, configuration files, and
if you are using SharePoint mode, the SharePoint content databases.
If you do an in-place upgrade from SQL Server 2008R2 to SQL Server 2014, then everything should work as expected.
Does Fluent Migrator not support SQL Server 2014?
I am getting below exception -
“The major version of the database server could not be determined or is not supported by FluentMigrator.”
Update: As of 2014-12-31 Fluent Migrator does support SQL Server 2014.
No, As of today (15.Dec.2014) Fluent Migrator doesn't support SQL Server 2014 version.
You can verify it in below wiki page.
https://github.com/schambers/fluentmigrator/wiki/Supported-Databases
Both yes and no. There is no explicit support yet but for 90% of features, it is the same code for Sql Server 2005, 2008, 2012 and 2014. If you specify the provider (see Command Line options here) as Sql Server 2012 then your migrations should work.
migrate --configPath "WithConnectionString.config" -conn "Test.Connection" --provider sqlserver2012 --assembly ".\Migrations\bin\Debug\Migrations.dll"
New features in Sql Server 2014 will not be supported but at this stage every new release of Sql Server contains few new features that affect FluentMigrator. For example, the only new features that Sql Server 2012 introduced and that affected FluentMigrator were sequences and clustered indexes. Here is the Pull Request for Sql Server 2012.
If there is a feature from Sql Server 2014 that you want support for then create an issue on Github!
EDIT: I installed Sql Server 2014 and tested that it works with the provider set to SqlServer2012. And it does!