Customer experience | Sales, Customer Insights,...

Dynamics CRM v8.2 - Guide to upgrading SQL Server 2012 to 2016

(0) Share

Report

Posted on by Community Member Microsoft Employee

I have a customer with Dynamics CRM v8.2. Their databases and reporting services are on a single server running Windows Server 2012 R2 and SQL 2012 Standard.

I would like to either

Perform an in-place upgrade of SQL Server and then an in-place upgrade of Server 2012 R2 to Server 2016.

Install SQL 2016 on another server running Server 2016 and transfer all databases and reports.

I can't find any guidance on this for Dynamics specifically. I see there are SQL guides but not sure what implications there are in doing this.

The customer cannot upgrade Dynamics version at this time.

Any help would be appreciated. Thank you.

All responses (4)

Answers (0)

Suggested answer

Pedro Cadavez de Fr... on at

Like (0)

Report

RE: Dynamics CRM v8.2 - Guide to upgrading SQL Server 2012 to 2016

Hello Apocalypse,

I'm mostly referring to challenges on in-place upgrading CRM server + CRM database itself.

Since you are just in-place upgrading OS and SQL , those doesn't exist.

Don't see a problem then with your approach.
Community Member Microsoft Employee on at

Like (0)

Report
RE: Dynamics CRM v8.2 - Guide to upgrading SQL Server 2012 to 2016

Hello Pedro

Thank you for your help. Can you explain what additional challenges I might face?

In the test environment:

I'm going to use VM snapshots on the database server to enable roll-back if it doesn't work.

Shutdown the other VMs' services using Deployment Manager.

Perform an in-place upgrade of SQL Server and then an in-place upgrade of Windows Server 2012 R2 to Windows Server 2016.

Test and see.

Failing that we'll look at the migration approach.
Suggested answer

Pedro Cadavez de Fr... on at

Like (0)

Report

RE: Dynamics CRM v8.2 - Guide to upgrading SQL Server 2012 to 2016

Hello Apocalypse,

Hope you are well.

In-place upgrades might work, but that could add additional challenges.

We find easier to deal with a new environment migration.

You can reuse here the following thread as still contains information that is still valid:

community.dynamics.com/.../migrating-dynamics-crm-2011-database-to-another-server

In summary:

- Install CRM in the new Server

- Backup DB from old server

- Restore on the new SQL server

- Import DB into CRM

The MSCRM_config DB cannot be reused on the new deployment, as that contains information unique to each deployment, like machine names and similar.

Let us know if there are still doubts.
edmunch on at

Like (0)

Report

RE: Dynamics CRM v8.2 - Guide to upgrading SQL Server 2012 to 2016

What is your customers current build of Dynamics CRM and what build do they plan go upgrade to?