SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Better Licensing for SQL Server


Better Licensing for SQL Server

Author
Message
David.Poole
David.Poole
SSCertifiable
SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)

Group: General Forum Members
Points: 7873 Visits: 3290
I'd say the pay for what you use process would work well allowing some synergy for cloud based costings.
The thought of being able to choose features rather than editions apeals. Quite a few people would like to have compression as an option without full-on enterprise edition

LinkedIn Profile

Newbie on www.simple-talk.com
SQLRNNR
SQLRNNR
SSC-Dedicated
SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)SSC-Dedicated (33K reputation)

Group: General Forum Members
Points: 33116 Visits: 18560
David.Poole (12/17/2012)
If you can't understand the licensing model then how can you be sure you are in compliance with it?

I've actually had two conversations with different Microsoft resellers who contradicted each other on licencing so if the resellers don't get it then how can anyone.

As with all legal documents the licences seem to be written to give the legal team a hard on rather than to communicate useful information to customers.


I have run into the same problem. It certainly doesn't make matters any easier. If the documents were published, then the whole thing would be a lot less confusing.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

Scott D. Jacobson
Scott D. Jacobson
SSChasing Mays
SSChasing Mays (632 reputation)SSChasing Mays (632 reputation)SSChasing Mays (632 reputation)SSChasing Mays (632 reputation)SSChasing Mays (632 reputation)SSChasing Mays (632 reputation)SSChasing Mays (632 reputation)SSChasing Mays (632 reputation)

Group: General Forum Members
Points: 632 Visits: 1017
As I was first reading Steve's editorial I was thinking, "Sure that would be nice but they probably don't have the resources to throw at it. Nice-to-haves don't usually get priority even when you're the size of Microsoft." But the more I thought about it and read everyone's responses it dawned on me. Amazon must know since they now offer SQL server. MS must know in order to properly price Azure services. So it follows that it shouldn't be that hard to institute Steve's suggestions. Maybe changing the entire model is in order. Maybe it should be pay-per-feature. At least they need to consider something different in this space. It's been far too difficult for far too long and has only gotten more complex over time.
peter-757102
peter-757102
SSC Eights!
SSC Eights! (861 reputation)SSC Eights! (861 reputation)SSC Eights! (861 reputation)SSC Eights! (861 reputation)SSC Eights! (861 reputation)SSC Eights! (861 reputation)SSC Eights! (861 reputation)SSC Eights! (861 reputation)

Group: General Forum Members
Points: 861 Visits: 2559
Scott D. Jacobson (12/18/2012)
... Maybe changing the entire model is in order. Maybe it should be pay-per-feature. At least they need to consider something different in this space. It's been far too difficult for far too long and has only gotten more complex over time.


While a pay per feature it seems a reasonable model for say an individual customer needing features X and Y, the world is more complex then that. It would be a disaster for standardization and code/solution exchange (which is already an issue). And it would be bad for multiple parties working on the same platform for the same customer as they all would need to be in synch database feature wise. It complicates matters in the developing process beyond what we have now.

For the same reasons I am strongly opposed to differentiating a product line (standard/enterprise/…) based on anything that you can programmatically do. Instead they could differentiate in matters of capacity or optional management/ security features, think for example of backup compression.

Right now, the standard editions of SQL Server are already severely handicapped compared to the enterprise editions. Things like table partitioning, compression, column store indexes or star join optimizations are not present in the standard editions. The huge gap in pricing between the standard and enterprise editions won’t for most customers justify the jump to that more expensive edition.

And as most people truly start to learn during their work, a whole generation of developers grows up never using these features or are even totally clueless about their existence. All Microsoft does with their licensing and product segmentation is handicap their product and in the market give competitors ample time to catch up.

It is strategically dumb…if only they were as paranoid as Google is for the emergence of new competitors! And in the end, only the paranoid will survive they say!
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search