RSS

Tag Archives: SQL Server

Transition SKU’s for CRM Hoster’s Available Thru October, 2019

For Dynamics hosters worried about all the changes with CRM have until October 31, 2019 to license the transition SKU’s in SPLA.

Although good news and provides some flexibility, the transition pricing is still higher than current CRM licenses.  As an example, Basic CRM SKU transition pricing for Customer Service is almost double!

Transition pricing is available to ease transition to the new Dynamics 365 pricing model.  It is also designed for current CRM customers, not new customers.  To learn more about Dynamics 365, please check out Dynamics 365 Licensing for SPLA

Thanks for reading,

SPLA Man

PS- Dont forget to license SQL and Windows with CRM!

 

Advertisement
 
Leave a comment

Posted by on May 15, 2017 in CRM, Dynamics 365

 

Tags: , , , , , , , , , , ,

Azure Stack, SQL Stretch Database and the Hosting Summit

Last month, Microsoft held their annual Hosting Summit in Bellevue, WA. The good news is SPLA is not going away. Last quarter marked the 20th straight QTR of double digit growth for Microsoft SPLA. What is changing is the competitive landscape. Microsoft does not see SPLA partners as a competitor per se, they see SPLA as one of the biggest competitive advantages over other cloud offerings (IBM, AWS, Google, etc). They have over 30,000 SPLA partners worldwide, and they believe they can leverage those 30,000 partners to offer different cloud solutions.

Microsoft is betting big on what they define as “hybrid cloud” and that’s where they see service providers (SPLA) playing a significant part. Hybrid cloud is not just offloading workloads from on premise to another datacenter, it’s about leveraging different technologies to deliver solutions. As an example, late last year Microsoft offered solution called “Azure Stack” You can read about it here.

It’s the same APIs and same code as what Microsoft delivers through Azure. From a licensing perspective, Azure Stack is cheaper through SPLA (Windows) than it would be to pay through consumption. It will be available to offer this summer through the hardware manufacturers but you can download it now to test out.

The other big bet is SQL, and especially around the feature of stretch database. In laymen terms, it’s taking data that is not often consumed and offloading it to the cloud, reducing resources and consumption on servers locally.   You can read more about stretch database from our friends at MSDN

All said, it was good to meet old friends and say hello to new ones at this event.  If you were at the hosting summit and you did not have the chance to meet the infamous SPLA Man, email me at info@splalicensing.com.  Would love to learn more about your offerings and how we can work together to make licensing simple.

Thanks for reading,

SPLA Man

 
1 Comment

Posted by on March 27, 2017 in Azure, In My Opinion, SQL 2016

 

Tags: , , , , , , , , , , , , , , , , , , , ,

Epic Community Connect and SPLA

The healthcare community has increased concerns with the way they have deployed (and licensed) their electronic medical record (EMR) software such as Epic Community Connect and others.  As a reader of this blog, you know that when you deploy software for the benefit of a third party (non employee) SPLA must be part of the conversation.  The only exception to this rule is if you actually own the code to the software you are hosting.  In other words, if you developed the software, you can use your own volume licenses to host your software.  If you host a third party software (such as Epic) you must license this in SPLA.   In most cases, many healthcare companies do not own the application, but lease it from the EMR vendor.

Rewind a few years and let’s pretend you are a large hospital who partnered with Epic to provide best in class patient record management for your clients, doctors, and other clinics. Your Epic deployment resides on a Windows Server, SQL Server, and RDS.  As the IT director, you purchased several server licenses and hundreds of Client Access Licenses (CAL) to cover all the external users.  You think you are covered; no one mentions you need to license this via SPLA.  Your reseller didn’t tell you, Microsoft didn’t tell you, and for that matter the vendor didn’t tell you.  You think all is well based off the information you received.  Fast forward 3 years and your volume licensing agreement is up for renewal.  Someone on the licensing side informs you that you shouldn’t true-up licenses or renew your agreement under volume licensing, you need to license SPLA.  You think that’s fine, if you must license under a different program who are you to argue. But what about all those license you already purchased and own?  Unfortunately, you cannot return them, you must allocate those internally.  You think to yourself that’s fine, except for one minor detail…. you purchased hundreds of CALs and you do not have hundreds of employees; those license you own are essentially worthless.  On top of everything else, you just received an audit notification.

Why would they receive an audit notification?  Once a vendor recognizes you have been under-licensed, the vendor might want to dig in deeper to see how long you have been out of compliant and if you purchased enough licenses to cover all the users.  In 90% of all audits, the customer is under-licensed.  Now you own licenses you don’t need, but should’ve purchased more because you don’t own enough licenses to cover all external users initially.  The vendor will want you to pay the delta of what you should’ve paid under SPLA and what you purchased under volume licensing (plus an audit fee).

If you are a healthcare provider and have been notified by Microsoft or any other vendor, please contact us.  We have found that in many cases the licenses report is not always 100% accurate.

Thanks for reading,

SPLA Man

 
Leave a comment

Posted by on October 12, 2016 in Compliance, EMR Software, Self Hosted

 

Tags: , , , , , , , , , , , , , , , ,

Worried about Windows 2016 Cores?

Yes, it’s the talk of the town.  “Windows 2016!  Oh my!  It’s moving to cores!!!”  That part is true.  What is NOT true is even when Windows 2016 is released, it doesn’t mean you have to license by core – you can still license by processor for all 2012 and earlier editions.  The catch?  Once your agreement expires and you sign a new SPLA after October 1st (when Windows 2016 is released) you must license by core regardless which version you are running.

So what does this mean to you?  If I was a service provider that reports over 2k in Windows and SQL licenses,  I might readjust when my SPLA expires to extend processor based licensing.   Wait…What?   You can readjust when my SPLA agreement expires?  Sure.  I’m SPLA Man.  Anything is possible with SPLA Man.

Thanks for reading,

Windows 2016 Man

 
13 Comments

Posted by on September 9, 2016 in Windows 2016

 

Tags: , , , , , , , , , , , , ,

Disaster Recovery Rights and License Mobility

 April 2015 PUR

Fail-over server rights do not apply in the case of software moved to shared third party servers under License Mobility through Software Assurance.

Example

Let’s say an end customer purchased a license with software assurance that qualifies for license mobility.  Since SA allows failover rights, most service providers (if not all) are under the impression they would get the same benefit in their datacenter as they would on premise.  In this example, the end customer transfers a SQL license over to the hoster, the hoster spins up a secondary SQL fail-over server.  Given the statement above from the PUR, If they are enabling SQL fail-over they would need a second license under SPLA.

 Why is this important?

For starters, compliance.  If that secondary server is not properly licensed or your under the assumption that if it exists on premise it must also exist in the cloud you are mistaken.

What about Cold DR?

Doesn’t exist anymore.

What about SQL Failover for SPLA specifically?

SQL SPLA licenses have fail-over rights.  Read the SPUR

What about other products for disaster recovery?

The SPUR has specific language around DR, how long the server can be active (non-production), when Windows would need to be reported, etc.

Any workarounds?

SAL for SA – I think this would fit well for DR.  Customer can still run the software on premise and spin up a second server in the cloud.

Normal SALs- 1 user SAL license can access multiple servers.  Could be another option if the customer is against license mobility.

In the words of a famous hoster “it’s not how you license…it’s how long can you get away with not licensing that really matters”  He was audited immediately following that statement.

Thanks for reading,

SPLA Man

 
Leave a comment

Posted by on April 30, 2015 in Disaster Recovery

 

Tags: , , , , , , , , , , , , , , , , , , ,

 
%d bloggers like this: