Lack of high availability features in Standard Ed | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Lack of high availability features in Standard Ed

What do you guys think about this? We all know that Enterprise Edition of 2005 is very, very expensive. But without it you cannot use any of the following:-
Database snapshots
Fast recovery
Online index operations
Online page and file restore
Parallel index operations
Updateable distributed partitioned views
Table and index partitioning I think it’s particularly TIGHT of MS not to put Snapshots in Std Ed. It’s not even a pure HA feature, it’s a reporting feature too. I guess they have to justify the astronomically high price of EE somehow, but it annoys me. Particularly when you work somewhere where they baulk at spending the £ on Ent Ed. Anyone else agree with this rant?
–SE v EE comparison

no the idea is to divide the world into 3 paid categories, low, medium and high
MS has to do decide which features should go into each category
In SQL 7/2000, it was reasonable to limit /3GB & AWE to Ent at the time of product launch,
but over time, the 2GB limit of Std became stupid, considering MS was very late with 2005, if you are not a high budget shop
backup your database, restore it with another name, or elsewhere
this is the poor/middle man’s snapshot people who paid lots of money can get instant snapshot personally, my feeling is some one who really needs snapshot probably did not architect their db correctly, and using this to compensate for his mistake
You’re so harsh! I disagree [about snapshots]. Imagine you’re mirroring and you’d like to use the mirror for reporting. Well you can’t! Unless you create snapshots of it. Yes I know it could have been architected differently. Trouble is I used to work for a charity where we got all MS licenses absurdly cheaply, so it’s a bit of a rude shock to be back in the commercial sector to discover licensing a high-end server with Ent Ed is going to be £60 grand. Know what I mean?
yes i can be very harsh, especially when my coffee is not done right on reporting, that is just my point, a properly architected database can do both transactions and reporting,
lack of skill on the architect is not a valid reason to cry to MS,
this is where vendors rake in the big money yes it is a rude shock to see prices in the commercial world
but you will get used to it, ask your users how important is it?
if it is not important in terms of ($$$, £££ or €€€) they are willing to cough up,
it is probably not worth your effort either let me give you an example of real world dilbert style
your company has 2 projects, and 2 project managers, one for each project you are brilliant in figuring out how accomplish your project for $100K with 2 headcount when a less imaginative solution might have been $1M with 10 people your counterpart is an idiot, his solution costs $2M with 20 people when it comes time for annual personnel evalutions
who is going to be ranked higher
the PM who managed the $100K project with 2 people
or the one who managed the $2M project with 20 people?
Was your coffee not right this morning? Not that I mind, the bluntness of your replies often makes me laugh. Obviously the $2 million project is far more impressive at Appraisal time.
what i say may sound stupid to you now
but over the course of time
i think you will realize MS is doing you a favor the Ent Ed price structure
(i don’t work for them, you should have noticed by now how liberally i distribute my critiques) MS is helping you become a big budget project manager
no joke
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by joechang</i><br />MS is helping you become a big budget project manager<br />no joke<br /><hr height="1" noshade id="quote"></font id="quote"></blockquote id="quote"><br />In some cultures, calling someone a project manager is considered derogatory.<br /><br />[<img src=’/community/emoticons/emotion-3.gif’ alt=’:eek:‘ />)]<br /><br />Roji. P. Thomas<br />SQL Server MVP<br /<a target="_blank" href=></a><br />
When did Joe joined MS<img src=’/community/emoticons/emotion-1.gif’ alt=’:)‘ /><br /><br />MohammedU.<br />Moderator<br />
i see many of you think i am joking
just watch who gets promoted in your company at some point,
you will realize
you must let go of your foolish notions of right and wrong
and do what it takes
otherwise your spouse may not be satisfied with your ability to provide
a reason lifestyle (read: mansion, luxury car, having enough clothes that they only have to worn once, 5-6 2 week exotic vacations per year, mingling in the right social circles, etc) now we are getting into luis’s post

I’m waiting for my spouse to provide me with that kind of lifestyle. Am I doing something wrong?
quote:Originally posted by joechang i see many of you think i am joking
just watch who gets promoted in your company

Same goes for the early starters (7am), working hard, leaving at 3pm, compared to the ones starting at 10am leaving at 6 or 7 pm filling their time reading papers, chit chat buzzwords, and deliver poor performing projects with poohah right on contract time but with a pile of fixes to be done afterward …
Guess who’s runnig away with "your" money …
Play nice guys, TGIF.
There is no point in using abusive language here, after all we all are here to help and be nice to each other. Tom
Your question is right on the difference of features between Standard and Enterprise, at the same time Microsoft has judged based on installation requirements that can vary widely, depending on users application needs. The different editions of SQL Server 2005 accommodate the unique performance, runtime, and price requirements of organizations and individuals. Now a days MS is pushing hard to promot 64 bit that will become the norm for SQL Server 2005 deployments. By raising the limitations associated with the 32-bit platform, you have the opportunity to upgrade to a highly scalable, consolidated environment. There is no doubt that SQL 2005 has brought lot of opportunities and enhancements in terms of performance, security & availability as compared to the previous editions. I believe the necessity of high availability & business continuity vary with the available editions, where in this case you need to go for Enterprise edition (high costs) and cannot rely on standard edition. We (at workplace) have had such requirement and forced the MS consultants to reduce the costs on licensing and
few main reasons to choose Enterprise over the Standard Edition are for scalability and availability requirements. At the end of the day it is upto the Budgeting to decide about spending $ millions should get the service delivery to 99.99%. On the topic refer link. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.