How Do You SKU?

KKline — Wed, 30 Mar 2011 14:49:00 GMT

I’d like your opinion here.

Follow my logic here for a moment as I walk through a couple rhetorical questions. Have you ever had a friend developed an application entirely on SQL Server Developer Edition? (Not that YOU would ever do such a thing, but maybe you know someone who has. Right?) And has your friend’s IT department actually deployed said application only to discover that they’re only licensed for Standard Edition in their production environment? And then was your friend’s IT management team is horrified to learn that they’ve either got to go through the very expensive process of extracting all of the Enterprise and/or Datacenter Edition features for the production application in order to remain in compliance, upgrade to the more expensive SKU licenses, or risk a potential future audit?

I’m not saying that this has happened to any of us. We’re too smart for that, after all. But have you ever known anyone who’s had this experience?

Having worked with a lot of customers another commercial RDBMS platforms (which I’ll euphemistically call “SEER” from Redforest City and “IB4” from Upstate City), I can tell you that auditing is a fun and exciting way for those platform vendors to make a LOT of money. This is especially true because a production application, once successfully deployed, tends to be too valuable to disable or otherwise compromise because high-end features slipped in to the development cycle even though the production environment only a “standard edition” SKU in place. Ouch! Talk about being caught between a rock and a hard place. Now, keep in mind that this is a strategy used by SEER and not by Microsoft. But Microsoft could implement the same sort of licensing audits if they wanted to. (Please leave a comment here if you have ever been audited. I’d love to hear your experiences, at least as much as NDA’s allow).

So if you use SQL Server Developer Edition (DE), of any version, would you like to see a feature that enables you to run DE not in its default “full featured mode” but at another SKU level, such as good ol’ Standard Edition? I know I would.

If you’re on the same page as I am, there are a number of suggestions logged on Connect about this very feature! Make your voice heard! Check out:

https://connect.microsoft.com/SQLServer/feedback/details/496380/enable-sql-developer-edition-to-target-specific-sql-version

Of course, the more skeptical reader might say “Hey, that’s their tough luck. Developers should know the difference in the SKU licensing options and feature sets of whatever SKU they’re developing on compared to what they’ll deploy on.” And I wouldn’t fault you for saying so.

But I would go on to point out that much of Microsoft’s success in enterprise IT settings can be traced back to their very strong relationship with developers. And anything that Microsoft can do to empower developers to save time, money, and resources during the development phase of an IT project in turn energizes that relationship between developer and Microsoft.

It also makes the life of the DBA that much easier, because they don’t need to imply that those cowboys on the development team went off half-cocked again. So what’s your opinion? Should SQL Server Developer Edition include a feature that sets the SKU-level of the database engine?

My Last "Catch-Up" Post for 2010 Content

KKline — Fri, 31 Dec 2010 20:57:00 GMT

I did a lot of writing in 2010. Unfortunately, I didn't do a good job of keeping all of that writing equally distributed throughout all of the channels where I'm active.

So here are a few more posts from my blog, put on-line during the months of November and December 2010, that I didn't get posted here on SQLBlog.com:

1. It's Time to Upgrade!

So many of my customers and many of you, dear readers, are still on SQL Server 2005. Join Kevin Kline, SQL Server MVP and SQL Server Technology Strategist for Quest Software and Brent Ozar, SQL Server Domain Expert for Quest Software as they introduce the top ten features and capabilities in SQL Server 2008 that they find to be the most exciting and valuable.

2. Dealing with the Micromanaging Boss

This is probably my favorite professional development article of the year. Micromanagers make us feel untrusted and stymied by their constant need for tediously detailed and frequent updates, constant changes to minor details of our work, and overly developed attention to administrative details that really don’t matter in our daily job. But there’s hope! Get all of my career advice on dealing with micromanaging bosses here.

3. [Video] Troubleshooting Memory Pressure on SQL Server

This is a little bit of an older video. But it's still useful info if you're working with SQL Server 2005 or 2000. Check it out here.

4. [DBTA] What the Heck is Microsoft's Database Product Trajectory?

I was once asked what I thought Microsoft's overall product trajectory for SQL Server was, in light of Oracle's rather obvious trajectory of acquiring multiple application vendors who will, in turn, deploy more and more of their applications to the Oracle database platform. You can read all about my thoughts in my monthly column at Database Trends & Application magazine - [READ MORE]

5. Eight Characteristics of Excellent Leaders [Plays Well With Others]

In this installment of my professional development column called Plays Well With Others, I talk about what distinguishes truly great leaders. There's a lively discussion on the topic and I encourage you to take part. Read it here.

6. The Shape of Database Licensing Costs to Come [DBTA]

One fall semester many years ago, I was a university freshman. Actually, I was anything but "fresh." I was dumb enough to think that 8 a.m. was a wonderful time to attend Economics 101. After staying up until the wee hours most every night, the "dismal science" took on more than one meaning as I set my clock just early enough to get to class on time. Along with 30 other very naïve classmates, I staggered into class and did my bleary-eyed best to focus on the lessons at hand. There were lots of Greek compound words and lots of graphs.

I learned, for example, that the word economics derives from the Greek "oikonomikos," which means, approximately, "death by slidedecks" and, specifically, "house" (oikos) and "management" (mikos). I barely survived the experience and never took an 8 a.m. class again. Imagine my surprise, then, when a lesson I'd learned (and promptly forgotten) all those years ago jumped back into my consciousness late last year. - [READ MORE]

7. So You're the Boss Now... [Plays Well with Others]

If you have any ambition at all, you have probably wanted (and possibly gotten) a promotion over your current colleagues. If you've been there before, you know that once friendly relationships can get, well, weird. Read my tips and tricks for how to make the most of this situation in this professional development article.

8. The NoSQL Movement - Hype or Hope?

NoSQL is no fad. And you need to be in the "know", not necessarily in the "No". Gno? Pneu? Too many phonetically similar pronunciations! Read my thoughts on the NoSQL movement on one of Database Trends & Applications magazine's most popular articles of the year. - [READ MORE]

9. Effectiveness and Efficiency at Work [Video]

In this golden oldie (yes, two years constitutes "old"), I present my thoughts on how to be both effective and efficient on the job and in life in general. And if you didn't know that these are different concepts, then you need this video most muchly.

10. What's Your Data Management and Retention Policy? [DBTA]

If managing your corporate data for the long term isn't currently on your mind, it should be, and in several different ways: cost, performance, business continuity, and compliance. [READ MORE]

Follow me on Twitter!

Originally Posted on YoutTube November 12, 2008.

Search results matching tags 'Developer', 'Administration', and 'Opinion'