Источник:
https://crmtipoftheday.com/1238/pain...e-from-8-to-9/
==============
Do not pass Go. Do not collect $200
Chance and Community Chest card
When planning upgrade of your 8 or 8.2 on-premises instance to version 9, there are two rules:
- Do not, I repeat, do not consider in-place upgrade.
- Raise a support ticket and get yourself a build 9.0.02
If you are using VMs either on-premises or in Azure, or if you have spare physical capacity, always, I repeat,
always go for the first option which is
Migrate by using a new instance of SQL Server. Why? Because it’s painless and fast. Do you really run your current version on Windows Server 2016 and SQL Server 2016? I’m asking because
both are required. You don’t have to go through painful upgrades if you opt for a new instance. Just install RTM build, add the 0.02 patch (is it like $0.02 patch?!)
Why to create a support ticket? Because if you use RTM build of version 9, changes are that during the organization upgrade you will receive an error message at the last mile:
Error : The AttributeLookupValue (Id=81cde1dc-2241-db11-898a-0007e9e17ebd) entity or component has attempted to transition from an invalid state
Build 0.02 takes care of that nasty error and for every single version 8 or 8.2 databases we imported so far, the upgrade did take a bit of time but it went as smooth as butter.
Источник:
https://crmtipoftheday.com/1238/pain...e-from-8-to-9/