Performance bench marks for CRM 2015 and CRM 2016

(0) Share

Report

Posted on by Community Member

Hi All,

May you provide white papers that speak towards Performance bench marks for CRM 2015 and CRM 2016 that is more infrastructure related?

I am expecting a document similar to CRM 2011 white paper with Intel and Dell Servers (www.microsoft.com/.../details.aspx)

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

Aiden Kaskela 19,696 on at

Like (0)

Report

Hi,

Here are some links for 2015/2016 performance and scalability, which may have what you're looking for. I don't think you're going to get the same type of infrastructure documentation as 2011 since Microsoft is really pushing the Online model

www.microsoft.com/.../details.aspx

Hope this helps! I'd appreciate if you'd mark this as Answering your question.

Thanks,

Aiden

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Aiden,

Thanks for your time. I have gone through documents mentioned earlier. Mentioned documented does not have any comparative study between CRM 2013 , CRM 2015, CRM 2016 machines. May you provide any document which have benchmark results of each results.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi All,

we are planning to migrate CRM 2011 on-premise system to CRM 2016 on-premise system.

if we follow ,migration upgrade , i need to follow have follow below process.

1. Take Backup of CRM 2011 SQL DB, Copy Back up file, restore to CRM 2013 SP1 Server

2. Create a CRM 2013 org from Restored file -> Take Backup of CRM 2013 SQL DB, Copy Back up file, restore to CRM 2015 Server

3. Create a CRM 2015 org from Restored file -> Take Backup of CRM 2015 SQL DB, Copy Back up file, restore to CRM 2016 Server

4. Create organization from CRM 2016 server.

I am thinking of planning my migration by clubbing migration upgrade + In place upgrade.

Below are steps I am planning.

1. Take Backup of CRM 2011 SQL DB, Copy Back up file, restore to CRM 2013 SP1 Server

2. Create a CRM 2013 org from Restored file -> Update CRM software to CRM 2015 -> Update CRM software to CRM 2016.

Are there any issues with my approach. I am not seeing any one suggested this approach of mixing both migration upgrade from CRM 2011 to CRM 2013 and In place upgrade from CRM 2013 to CRM 2016. I need your inputs on pros and cons of this approach.

Was this reply helpful? Yes No
paulmcquillancrm 40 on at

Like (0)

Report

Hi there,

Yes, you need to import the 2011 DB into 2013, then import into 2015, and finally into 2016.

Having done this recently, I would recommend the following:

1. Leave your original on-prem build of CRM 2011 in place - simply export the DB

2. Import the DB into a Dev/Test Environment of 2013

3. Do the 'hops' of importing into 2013, 2015 and finally 2016 in your Dev/Test Environment (recommend do this using VM Servers)

4. This gives you a test environment to check that your Customisations, Javascript, Workflow and Plugins are working in the new version of Dynamics - plus review if any of your existing functionality could or should be redeveloped with 2016 in mind, say using a Business Rule or Synchronous Workflow instead of a Plugin. (I've yet to see a build of Dynamics CRM that does not benefit from a good Business Process Flow for the Opportunity, Case or Campaign entity!)

5. Build your new on-prem build of CRM 2016 alongside the existing 2011 build

6. Export your CRM 2016 DB from Dev/Test and import into your new Setup - however import this as a New Organisation for UAT Only.

7. Invite your team or client to run UAT Testing / Training with 2016 using this UAT Organisation.

8. Once the green light has been given to go live - take another backup of the 2011 DB and run it through the hops from 2011 to 2016 and then import into your new live setup as the Live Organisation. (mapping any DNS or Addresses to point from the original 2011 Server to the new 2016 Server)

The reason I would recommend having all the Dev/Test Servers on stand by is that this allows you to repeat the process - once for UAT and Testing, and next for Live; as this will flush out any problems and so ensure that your go-live evening/weekend is a known process and so likely to go much more smoothly.

Apologises if any of the above is already in your plan - but hopefully helps break down the steps we found useful when running 11 --> 16 upgrades.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Paul,

Thanks for details. What is your view/suggestion on Approach 2 mentioned in the question?

1. Take Backup of CRM 2011 SQL DB, Copy Back up file, restore to CRM 2013 SP1 Server

2. Create a CRM 2013 org from Restored file -> Update CRM software to CRM 2015 -> Update CRM software to CRM 2016.

Are there any issues with this approach. I am not seeing any one suggested this approach of mixing both migration upgrade from CRM 2011 to CRM 2013 and In place upgrade from CRM 2013 to CRM 2016. I need your inputs on pros and cons of this approach.

Was this reply helpful? Yes No
paulmcquillancrm 40 on at

Like (0)

Report

My concern would be that once you have done the in-place upgrade, it will be tricky to go back and do a 2nd pass if any problems or rework comes out of UAT or Go-Live . (unless you use VM Saved States / Snapshots on your Servers if they are virtual)

So if you are doing a Test Upgrade before the Live Upgrade, you would need to repeat the upgrade process at least twice - would could be slower than having a conveyer belt of 13, 15 and 16 servers waiting to run through the upgrade. (as once you have the 'conveyor belt' setup, you can bosh your Database through quite quickly)

As the jump to 2016 is quite vast for Training and Testing, would definitely recommend having a solid process of upgrading a UAT/Test Environment first to then let your Users or Client loose on 2016 before gaining their approval to do Live.

So I think both approaches should work, but think having a set of CRM Servers that you can repeat the upgrade on would be more sustainable.

Was this reply helpful? Yes No