Migrating from (mostly) 2K8 to 2016

Question

Post reply

Migrating from (mostly) 2K8 to 2016

JaybeeSQL

Hall of Fame

Points: 3501
More actions
May 18, 2019 at 1:23 pm

#3644981

HI all,
About to start this project and would be grateful for any good comprehensive articles rated highly by the good folks here at SSC 🙂
TIA

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Jeff Moden SSC Guru Points: 1003894 More actions · Answer 1

In place migration or migration to a new server?

Any partitioned tables?

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Thom A SSC Guru Points: 99126 More actions · Answer 2

You say mostly 2008 servers, any older than 2008?

Thom~

Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk

JaybeeSQL Hall of Fame Points: 3501 More actions · Answer 3

I haven't seen the estate yet, presumably a mixture of in-place and new build. Nothing older than 2K8. Unlikely (but not impossible) they have partitioned tables.

This reply was modified 4 years, 11 months ago by JaybeeSQL.

Jeff Moden SSC Guru Points: 1003894 More actions · Answer 4

Since this is a huge subject and you don't yet know the lay of the land, see the following. You should read it (especially about the migration assistant) even before the "estate" is known.

https://docs.microsoft.com/en-us/sql/database-engine/install-windows/upgrade-sql-server?view=sql-server-2017

There's also been a shedload of articles on the subject of migration because SQL Server 2008 is going out of support. Google is your friend here.

The only extra help I can offer after having gone through this about 3 years ago is to say make sure you can recover as if a nuke hit your data center. If the system being migrated has any special features going on (especially when it comes to DR and data transmission but includes things like partitioned tables), you might want do some serious testing first. In other words, consider NOT doing in-place upgrades. If you have to do in-place upgrades, make real sure that you can "go back" easily, quickly, and properly.

And, yeah... plan on this being done during an outage. Even renaming a system has some nasty catches in the throat.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Grant Fritchey SSC Guru Points: 398715 More actions · Answer 5

Also, the biggest pain point in upgrades from pre-2014 to post-2014 is the new cardinality estimation engine. Most queries are unaffected. Some queries benefit. A few, suffer greatly. Plan to test accordingly. Since you're doing the right thing and skipping 2014 entirely (and honestly, if I were moving everything, I'd move it all to 2017, not 2016), you get Query Store. Be sure to use it for the upgrade process, even if you don't use it after you upgrade. The basics are simple, move the database, but don't change the compatibility level. Run your load for some period of time (hours, days, weeks, you decide) with Query Store enabled. Then, change the compatibility level. If any queries suffer from regression, use Query Store to force the old plan until you figure out what else you need to do to fix the queries.

"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