crm scalability? RRS feed

  • Question

  • Hello, what steps do you take to help make CRM scalable?  What steps would you take to make CRM massively scalable?  Are there any practical limits on the number of users or the amount of processing that should be handled by CRM?

    Wednesday, March 12, 2014 2:29 AM

All replies

  • Hi dotnetteramg,

    CRM can be made scalable depending on your requirement. While in some cases, it would be enough to have multiple load balanced Application servers; in some cases it might require more fragmentation thus separating each of the roles of Dynamics CRM. For example, if you have a lot of asynchronous processes and they get triggered in huge numbers, a good way would be to put the Asynchronous Processing Service role on an entirely different box, maybe even multiple boxes if required.

    You can go through the Implementation Guide for Dynamics CRM, where it is listed out. Following links are also worth checking:





    Admin QuikView Solution for CRM 2013

    Wednesday, March 12, 2014 9:37 AM
  • Just a thought on Asynch service, if I understand correctly, you can install it on a separate server, or you can put it on multiple load-balanced servers, but not both (a separate load-balanced cluster from the front-end). If you use NLB for CRM servers, every server in the load-balanced cluster must have at least the Application Server role and Organization service role, and must have all the same roles. I could be wrong, so if anyone is doing it differently, I'd love to hear...

    Useful article about Asynch on multiple servers:


    Scalability will depend on things like the impact of your security model and design choices. Read the white paper Scalable Security Modeling with Microsoft Dynamics CRM 2013 for good information about this.

    Performance depends on your application server design (eg hardware, load balancing - although generally load balancing improves High Availability more than it provides sheer performance gains), SQL server configuration (right down to optimal disk IO and up through things like index maintenance plans, using SQL 2012 Always on to offload reporting to a second server), client software and hardware, network performance improvements (eg using WCF compression combined with https if you have heavy use of the Outlook client) and so on....

    It's a huge topic really, and almost everything you do will be a trade-off between performance, cost, complexity (which leads to more cost and things like DR issues), and actual business needs.

    Hope this helps.
    Adam Vero, Microsoft Certified Trainer | Microsoft Community Contributor 2011
    UK CRM Guru Blog

    Wednesday, March 12, 2014 7:42 PM