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.
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.
is pronounced "ree-bar
" and is a "Modenism
" for R
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".
"If "pre-optimization" is the root of all evil, then what does the resulting no optimization lead to?"
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)