But think about libraries. Imagine a library that handles dates and times correctly. You probably need one for whatever you are doing. Would you pay for one? No of course not because this is a solved problem and just about any language has this built into their standard library. You could build your own but it would have no economical value. Because it is a commodity. There are countless examples like this.
SQL server is a great example. Buying SQL Server for a new project doesn't make any sense for most people. The only reason to use it would be that you are already using it or somehow stuck with it (because you work in some place with lots of legacy software). Otherwise, there are plenty of perfectly fine and free alternatives. Databases are a commodity. If you need one, there are dozen or so free mainstream alternatives. The economic value of new ones is very low unless they do something particularly novel. Which then promptly gets imitated by others. And I'm sure SQL server has a few nice bits and bobs that are amazing. But by and large most people would ignore it as an option at this point. I haven't touched it in twenty years myself. At the time we had a product that could use either mysql or sql server (and Oracle even). Mysql worked fine and there was little technical reason to prefer the other options other than some imaginary value that companies associated with it (like getting support that they would never use).