SQL Server licensing confuses most companies: 70% overspend or face compliance risk. Poor data quality is the first problem. You need to track at least 95% of devices running SQL Server to know what you actually owe.
Chapters
Actually, if you look at our website, our SQL licensing blog is our number one traffic web content. If you look at our YouTube site, our SQL videos are our top traffic YouTube videos. Like I said, it's a very, very common topic. The thing is, it's very confusing. Licensing model for SQL Server is confusing. In fact, our Data suggests that 70% of companies are either spending too much on SQL or have unknown compliance exposures. They're either spending more money than they should or they've got a audit risk lurking that they have no clue, no clue about. And the top reasons for that. We're going to explore all of these in some detail today. But, you know, those boil down into kind of these six main things. So this is what we see across all the engagements where we're helping customers with this. The first being poor data quality. Right. And so I say here that typically the data quality is less than 65%. And so what I mean by that, we're going to dive into this a little bit later. But when we talk about data quality, you have to think about, do I have inventory? So what devices are out there that have SQL installed and do I have inventory? And so from an inventory perspective, we want to see 95% of the devices that are out there having inventory.