January 19, 2018 at 6:49 am
Hi to you all,
i want to upgrade from sql 2008 to 2014 and that will be my first time.My question is do i need to run sp_help_revlogin on each database or just once on master?
What else do i need to script?
I am going to do backup and restore
Thank you God bless
January 19, 2018 at 6:54 am
You only need to run it once on master and then run the script that is created on your new instance. You will need to look at also scripting out any sql agent jobs you have.
Thanks
January 19, 2018 at 7:11 am
Thank you!
January 19, 2018 at 11:47 am
If you're backing up then restoring to a different server, there was a conversation about what all you need to consider when migrating like that:
http://www.sqlservercentral.com/articles/Editorial/154033/
January 19, 2018 at 12:56 pm
Don't do it.
Upgrading to SQL Server 2014 means making the leap to the new cardinality estimation engine (a very good thing, most of the time). If you hit edge cases in your code where the new CE causes problems SQL Server 2014 doesn't offer any tools to easily deal with it. SQL Server 2016 & 2017 have Query Store which deals with the CE issues better than any other method. I'd strongly recommend you upgrade to one of them instead.
After that, all the other answers are applicable.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 22, 2018 at 11:00 am
Grant Fritchey - Friday, January 19, 2018 12:56 PMSQL Server 2016 & 2017 have Query Store which deals with the CE issues better than any other method. I'd strongly recommend you upgrade to one of them instead.
+1, good advice here from Grant
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 23, 2018 at 10:54 pm
Grant Fritchey - Friday, January 19, 2018 12:56 PMDon't do it.Upgrading to SQL Server 2014 means making the leap to the new cardinality estimation engine (a very good thing, most of the time). If you hit edge cases in your code where the new CE causes problems SQL Server 2014 doesn't offer any tools to easily deal with it. SQL Server 2016 & 2017 have Query Store which deals with the CE issues better than any other method. I'd strongly recommend you upgrade to one of them instead.
After that, all the other answers are applicable.
Yep, Please upgrade it to SQL Server 2016 because you'd be having a lot of In memory features than 2014 version.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply