I wish developers in general would stop using the us vs them paradigm to consider the customer. Assuming the user is an idiot newb who can't be trusted with settings is wrong. Assuming the user has somehow managed to become an expert at internals and can be trusted with no safety net is also wrong.

I assume that if I asked any of the professionals in this SQLServerCentral community if I should change setting X, the most accurate answer would be "it depends" - and the ensuing discussion of pro/con and if-this-then-that would prove their understanding (and mine) of the how/why of deviating from the default.

If the UI for affecting changes to the system captured this expert advise and took a more conversational approach, I know I'd feel more confident investigating switches/dials because the UI itself would remind me "be sure you consider..." or "this will impact..."

I'm not suggesting to go so far as a hand-holding "clippy" virtual DBA, but if I'm attempting to tune SQL for high performance and the interface can provide me with a sanity-check about observed daily requirements being within normal expectations for default settings I'd like to see a message like "Are you sure you want to risk your current A-OK status for some perceived benefit you just read about online?" Yeah, I think that's a good idea. 🙂