|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Yesterday @ 2:52 PM
Points: 1,322,
Visits: 1,071
|
|
Re: Defaults
First off, I'm pretty sure there is some sort of team/committee for each Microsoft product that decides on what the defaults should be. I'm also sure that decisions reached by that committee aren't going to suit everyone, even those on the committee.
I think that for a product like SQL Server that is meant to be administered by a professional, there should be very few, if any, defaults. Instead of setting defaults and forcing the administrator to navigate through various menus to set up the server "properly" (i.e. the way he wants it) the install should present the ability to set all of the options right up front. Anything that isn't a gimme (e.g. ANSI_NULLS) should be required to be set.
Obviously, that doesn't work for desktop software. Desktop software should be defaulted to be usable right off the bat without any tweaking until you find something you really want to change.
As for the multiple ways to do things. Generally, it's good. But, I have seen a lot of people (and have myself been guilty of) get caught up in trying to pick the best option when any of several good enough options would have been fine. -- JimFive
|
|
|
|
|
SSC-Dedicated
           
Group: Administrators
Last Login: Today @ 4:46 PM
Points: 31,433,
Visits: 13,745
|
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Wednesday, May 01, 2013 9:44 AM
Points: 1,043,
Visits: 2,943
|
|
Agreed with the "executive decision".
I'd also agree with James that that's the way it should be, but if you make something only available to experienced professionals, a lot of potential buyers will simply not buy it. Microsoft simply couldn't afford to make a decision like that, so the result is a commercially necessary compromise.
Semper in excretia, sumus solum profundum variat
|
|
|
|