Now, DBAs come and go and systems get updated. Switches are good. But sometimes more importantly is you know what and more importantly why you want to toggle a switch.
A wise man once said that the role of a camera is to "get out of the way of taking the picture". I feel very the same about a DBMS.
If I could take a good picture by flipping the fewest if not no switches, the better; If there was a better way to configure my database and it'd run fine for most of the days, why not?
But don't get me wrong, switches are good for the small fraction of work you have to do, where you know best what you want. For everyday work, worrying about switches too much is just a pain.
Too many decisions to make can make for overload and confusion. Sometimes having the option available or more decision points available is a good thing.
_______________________________________________I have given a name to my pain...MCM SQL Server, MVPSQL RNNRPosting Performance Based Questions - Gail Shaw
Learn Extended Events