2 Replies Latest reply on May 21, 2018 6:54 AM by acmtix

    Microsoft Licensing Schemes


      Can others relate how they licensed the SQL database for their SolarWinds installation?  Can I assume that the core licensing model is now the way to go?
      We are preparing to do our first NPM/Orion installation and we were pretty excited about it.
      One of our team members on the SQL support side, suggested that we talk with Microsoft to make sure that we were licensing correctly.

      This turned out to be a huge mistake.  I personally feel that we are being cheated, but unfortunately, we have to use MS SQL if we want to use SolarWinds. 

      This is what we received from MS this morning:


      From: Chris Jardine
      Sent: Friday, June 20, 2014 10:10 AM
      To: Holub, Carol
      Cc: Gary Morris; King, Charles; Akonom, Philip; Fritzi Mulkey; Jack Westerlund; Jon Sonnen; Madison O'Kane; Elliott, Clay; Kim Fuqua
      Subject: RE: SQL Server Licensing Documentation/Fort Bend County TX

      Hi Carol-

      Shortly after the initial SQL conversations with Madison I did send the request to the Microsoft Licensing Desk for further clarification. Below is the information they provided. I have attached the product use rights (PUR) referenced below.

      “Hi Chris,

      This is a multiplexing scenario.  The SQL Server should be licensed Per Core.  The other alternative is to license all of the end points with SQL Server CALs…not just the cisco devices, but all devices that connect to the Cisco devices.  From a cost perspective licensing Per Core is a much better alternative.

      The use rights document is the Product Use Rights (PUR).  The use rights for the Server + CAL model, when it comes to the CAL requirement are quite simple

      Page 28- April 2014 PUR

      You have the rights below for each license you acquire.
      1.   You must assign each license to a single Server.
      2.   For each license, you may use one Running Instance of server software on the Licensed Server in either a Physical or Virtual OSE.
      3.   You may use the additional software listed in Appendix 3 in conjunction with your use of server software.

      1.   Except as described here and noted in the Product-specific license terms, all server software access requires CALs.

      Page 11- April 2014 PUR
      Hardware or software you use to pool connections, reroute information, reduce the number of devices or users that directly access or use the product, or reduce the number of operating system environments (or OSEs), devices or users the product directly manages, (sometimes referred to as “multiplexing” or “pooling”), does not reduce the number of licenses of any type that you need.

      When you combine the two:
      •        All Server access requires CALs
      •        Multiplexing does not reduce the number of licenses of any type that you need

      …the result is any number of devices that are being routed by a smaller number of devices…which then connect to the server SW…does not reduce the number of CALs required.”