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
Related
Can I create a snapshot from SQL Server 2012 on a SQL Server 2008 R2 Server?
The goal is to build reporting and queries without locking the live database.
I need only a DB copy (Getdate()-1)
No, the SQL Server 2012 snapshot has specific SQL Server 2012 features in it that are not compatible with SQL Server 2008 R2. These are incompatibilities that you will not see. They are deep in the SQL Server engine. You cannot do this.
It's a similar concept to trying to restore a SQL Server 2012 database backup to a SQL Server 2008 R2 instance. The higher database version cannot backstep to a lower version.
You need to use a SQL Server of the same level or higher (I believe or higher) for your snapshot server.
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
Can I use a SQL Server Express database backup file to restore that database on a full fledged version of SQL Server. I am particularly looking at SQL Server 2008 Express to SQL Server 2012 Enterprise. And if so how?
Lets be clear about one thing first, SQL Server Express , Standard and Enterprise are the Editions.
SQL Server 2005 , 2008, 2008 R2 and 2012 are SQL Server versions.
Now coming to your question whether you can restore a database from 2008 Express to 2012 Enterprise?
The Simple Answer would be YES you can.
A couple of things to keep in mind.
SQL Server Editions has no limitation you can backup and restore databases from one Edition to another without any restrictions (Except SQL Server Express which can only accommodate databases upto 10 GB). Other than this size limitation in SQL Server express, all is good.
Whereas SQL Server Versions has a very strict limitation, You can go up 3 versions but cannot go down at all.
For example if you had taken a backup on SQL Server 2008 (regardless of Edition) you can restore this backup onto a SQL Server 2008, 2008 R2 , 2012 and I think also on 2014. But you cannot restore this onto a SQL Server 2005.
I hope the explanation clears some confusions.
I have a new server and want to install SQL Server 2014 Standard and migrate my database across from my old server which runs SQL Server 2008 R2 (10.50.1600.1).
I have upgraded locally, but having to move servers on my production environment complicates matters, so I thought I'd ask about the best way to progress giving my situation. I can think of different options to do the upgrade, but I am not sure which is the best choice:
Would it be best to upgrade my current SQL Server 2008 R2 box with service pack 2 before thinking about the upgrade, or will this not make a difference if I'm upgrading? If I do, which is the best option below?
1) Install SQL Server 2008 R2 service pack 2 on the current server, upgrade in-situ with SQL Server 2014, perform backup. Restore SQL Server 2014 backup on new server.
2) Install SQL Server 2008 R2 service pack 2 on the current server, perform backup. Restore SQL Server 2008 R2 backup on new server on SQL Server 2014.
I understand that SQL Server 2014 includes new full text search features that are not available in 2008 which you are prompted for as part of the installation process, so I'm thinking that if I just restore a 2008 backup on 2014 I will not be 'upgrading' in full. Would it therefore be better to take option 1 (above) over option 2?
I did not find answer given by Aashish promising because he said
Restoring backup will not upgrade your database
This looks confusing. If you restore backup taken on 2008 r2 database to 2014 it would be upgraded automatically to 2014. After restoration change compatibility level to 120 and you are good to go.
Regarding upgrade from 2008 r2 to 2014 there are two methods
Inplace upgrade
Side by side upgrade
In place upgrade can be use when your environment is less complex. You need to make sure you first upgrade SQl Server 2008 R2 to SP2/Sp3( I would recommend SP3) and then run Upgrade advisor. Only when upgrade advisor does not finds any issue you can go ahead and do inplace upgrade.
Side by side upgrade is much safer but is time consuming and has rollback plan. The old instance is not touched. In this method you have to install new instance of SQL Server 2014 then migrate database using backup and restore method.
Then migrate logins using this Support article
Then migrate job using script out method of you can us SSIS transfer job task to migrate jobs.
Migrate linked server and other server objects using script out method.
Migrate SSIS packages if any.
After this you are good to go. Make sure after migration you rebuild indexes and update statistics using Ola Hallengen Index rebuild and update Statistics solution
Do let me know if any further information is required
-> Restoring backup will not upgrade your database.
So,
1)Microsoft SQL Server 2014 installation setup provide options to upgrade your database either from 2008 R2 or from 2012.
This will preform all the process and provide information if your database is upgrade able or you required to make some changes to your old database. After that you can proceed to upgrade database from 2008 R2 to 2014.
eg. Click Start, point to All Programs, point to Microsoft SQL Server 2014 , and then click SQL Server 2014 Upgrade Advisor.
For further details http://msdn.microsoft.com/en-us/library/ms144256.aspx
My recommendation would be to install SQL Server 2014 instance and then backup and migrate database from SQL Server 2008 R2 to SQL Server 2014
2) There are other third party tools that will preform all the necessary processes and messaging before upgrade.
I use SQL Server 2008 R2 as the database engine. With my MSDN subscription, I can get SQL Server 2012 for development use. Since I noticed some cool things in 2012 SSMS, my question is that if I only use 2012 SSMS and keep 2008 R2 as the database engine, will there be any difference in scripts' generation or any other effects?
Thanks.
UPDATE 1:
Oh yes, I saw this page: SQL Server Database Engine Backward Compatibility, but it is not exactly what I am looking for.
No, there should be no ill effects.
SSMS 2012 should generate scripts that are compatible with the database version that is being actively used.