Tip #1238: Painless upgrade 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:

  1. Do not, I repeat, do not consider in-place upgrade.
  2. Raise a support ticket and get yourself a build 9.0.02
    EDIT: download service update 0.3

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?!)

EDIT: ignore the rest as service update 0.3 is available for download.

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.

Cover photo by Paul Felberbauer

4 thoughts on “Tip #1238: Painless upgrade from 8 to 9

  1. Yvan Leclerc says:

    Great tip! Thanks!

    Microsoft released build number on April 4. Do we still need to get the 0.02 from a ticket with them?

  2. James R says:

    Hi George

    I guess I already know your answer but we have an environment with SQL 2016 and Server 2016 already set up so to me it would be a lot less effort to do an in place upgrade to take us from 8.2 to 9.x. I would interested to know if anyone else has tried it. We have test environments that we can try it on first prior to taking the plunge, if we decide to.

    • James,

      in this scenario your best bet is to do what’s called Migrate by using the same instance of SQL Server, i.e. new Dynamics 365 server and in-place upgrade for SQL. Just make sure you have the full SQL backup – that’d be the only thing to restore if things go pear shape.


Leave a Reply

Your email address will not be published. Required fields are marked *