Two SQL Server Instances - sql-server

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

Related

Migrate SQL Server 2008 databases to 2016

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

SSRS 2016 compatible with SQL Server 2014 db server

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.

What will be missed if report server 2008R2 database gets restored in SQL server 2014

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.

Transaction log shipping in different edition of sql server 2014

We are considering to upgrade our Database from SQL Server 2008 R2 to SQL Server 2014. However, The new licensing with Core based seem to be very expensive.
We have one primary database and one secondary database. If we have SQL Server 2014 Enterprise Edition for the Primary database and SQL Server 2014 Standard Edition for the Secondary Database.
Question 1)
Is it possible to run transaction log shipping in different edition as above?
Question 2)
Could it be possible to run it from SQL Server 2014 to SQL Server 2008 R2?
Is it possible to run transaction log shipping in different edition as above?
Going for possibility yes it is possible to configure log shipping between SQL Server 2012 Enterprise and standard edition. But Just think of scenario where you are using enterprise features in Enterprise edition and failover happens now SQL server is on standrad edition and enterprise features will not work and you might face issue with application, some functionality crashing. I dont think you want this.
Plus again if you are using enterprise features and to configure loghshipping you take backup of enterprise edition and try to restore it on standard it would fail saying the backup has enterprise features and DB cannot be brought online because current database does not supports it
Could it be possible to run it from SQL Server 2014 to SQL Server 2008 R2?
No because you cannot restore database backup taken on SQL Server 2014 on SQL Server 2008 R2. If you like to make SQL Server 2008 R2 as primary and 2014 as secondary then you may succeed in configuring logshipping using T-SQL scripts( you cannot do it using GUI) but consider scenario where failover occurs and 2014 is new primary you cannot fail it back to 2008 r2 as Higher to lower version is not allowed.
Hope this is clear

Migrating from SYBASE SQLAnywhere 11.0 to SQL Server 2008 R2 Express

Hello everyone i have got a project to migrate from SQLAnywhere 11 to any new relational databases for our ship crew web application.The reasons for migrating is cost and support issues.I will need to choose a database which is free and has all features as SQLAnywhere 11.0.
Here is the list of Questions i want to know about SQL Server 2008 R2 express.
Do we have any migration utility to move from SQL Anywhere 11 to SQL Server 2008 R2 express.
How easy is deployment of SQL Server 2008 R2 express from install shield MSI.
Alternative methods to migrate from SQLAnyhere 11 to SQL server 2008 R2 express.
Do management tools come free with express addition. I should be able to defragment and restore the database.
Thank you
There is a SQL Server Migration Assistant (SSMA) for Sybase (v 5.1 was released just this week), but I am not familiar enough with SQL Anywhere to assure you whether, or how well, it works:
http://blogs.msdn.com/b/ssma/archive/2011/07/12/announcing-sql-server-migration-assistant-ssma-v-5-1.aspx
Deployment of SQL Server Express is relatively easy, but I haven't done any work recently incorporating this into a more complex installer.
If you use Express w/Tools or Express w/Advanced Services, they come with Management Studio Express. You can also download this separately:
http://www.microsoft.com/download/en/details.aspx?id=22985
Note that Management Studio Express is missing some of the SSMS functionality, such as managing agent, so if you have to manage other editions you may be better off investing $49 (or less, depending on vendor) into the developer edition, which comes with the full version of SSMS.

Resources