Multiple instances of CRM against a SQL Server cluster - VMWare/licensing issues RRS feed

  • Question

  • So, as so many others, i need to set up two different CRM servers. Our IT department cater to a diverse set of organizations, and all though we'd love to have them all as different organizations in one CRM server, that is not possible since we find our selves in situations where one part of the organization wants to upgrade to a new version of CRM but the other will not. Given the enormity of changes between some roll-ups, that is quite understandable.

    So, we need two servers. No problem, all of our stuff is virtualized anyway, so we'll create a new VmWare instance, install a licensed CRM server on that and voila. Almost. We'd like them both to use our very nice SQL Server Cluster. Since the SSRS server is currently installed on the cluster, and two CRM servers can not share an SSRS server, that's a stopper.

    No worries, we move the SSRS server off the cluster an onto the CRM server instead. Seems a reasonable. Technically, the way I understand it, this should be doable. HOWEVER.

    The SSRS server is licensed as the SQL server, which seems to mean that we need to pay a full SQL Server license for each of the Dynamics CRM servers, even though they do not contain any SQL Servers. Not only that, with the Microsoft license situation on virtual machines, we'd have to license an SQL Server for each of the VMs running on the ESX box we have. That's a lot of VMs, and most of them have nothing to do with CRM, SQL Server or anything.

    If my analysis is inaccurate, can someone please tell me how we can do this? If it is accurate, is everybody who works with licensing at Microsoft gone completely insane?

    Wednesday, October 9, 2013 8:28 AM

All replies

  • I don't think I have the answer for you but I can clarify your scenario and question.

    For each server that has CRM you require a CRM server licence (regardless of whether it is in the same or different deployment)

    Each deployment of CRM requires a separate instance of SQL Server (on the same or different SQL Servers) because each deployment has a MSCRM_CONFIG database and there can only be one for each SQL instance.

    Each deployment of CRM requires a separate instance of SQL reporting services.

    The problem arises when you install the CRM reporting extensions on a server because it can only be installed once and can only serve one instance of SQL Reporting Services.

    So, in your case because you have more than one deployment you are forced to have SQL Reporting Services on a separate server for each CRM deployment.

    Your question is then, how is SQL Reporting Services licensed?

    I suspect it depends on the version and edition of SQL Server that you have. What are they?

    Thursday, October 17, 2013 7:57 AM