SPLA is the only Microsoft Licensing vehicle where the Service Provider can true-up or down on a monthly basis. It also allows a hoster or ISV to change editions on a montly basis. With that in mind, we’ve put together some potential options you might be able to leverage during periods of low utilization, to reduce your SPLA spend.
SQL Server
Many times, deployment of specific SQL Server editions is driven by system and/or feature requirements. Conversely, just as often we see that service providers standardize their SQL Server image and over deploy the high-end edition(s) of the software. In both instances, however, IT Staff and Architects often overlook the option of utilizing the Web edition of SQL Server. This software does have licensing and technical limitations but it’s a great fit when the need is for a database to support web pages, web sites, web applications and web services. ISVs, in particular, are encouraged to evaluate the feasibility of SQL Server Web Edition, especially when a considering a database solution for proprietary web apps.
Here are the SQL Server Web Edition terms found in the Services Provider Use Rights document:
The software may be used only to support public and Internet accessible Web pages, Web sites, Web applications and Web services. It may not be used to support line of business applications (e.g., Customer Relationship Management, Enterprise Resource Management and other similar applications).
You can also find a detailed SQL Server Edition comparison here.
One other thought when it comes to SQL Sever Standard. It’s the one edition of Core-based Server software that also offers hosters the choice of licensing it per user (Subscriber Access License). It’s best to evaluate this licensing model for small clients, where direct or indirect access is limited to a small number of users.
Both the Web Edition and SAL options, where applicable, can help you reduce your SQL Server spend up to 90% while delivering the same level of service.
Subscriber Access License (SAL) Software
Given that SAL-based software is licensed by permitted access vs. consumed services, consider restricting permissions to your SaaS solution(s) for products such as Office in order to decrease your reported license usage. Such a reduction will be a flection of your current situation and can be implemented, as an example, by updating your Active Directory Security Groups to define access roles. This can be updated month-to-month and will allow you to bring clients back online as needed.
Developer Tools
Consider moving your development practice to a large public cloud provider. Rather than dedicating and licensing infrastructure in your datacenter, you can spin up VMs as needed and only pay for the number of hours you consume the service. Azure is a great example of this type of solution and it’s the only one you can deploy your MDSN licensed software to.
We would be more than happy to walk through your unique scenario, in a no-strings attached, complimentary consultation. We are committed to supporting the Service Provider community during these harsh economic times. Click below to schedule an appointment.
From your Microsoft Licensing Experts at Altaris Cloud