you seem to not have ever been in a situation where TB3 is used this way. Until you actually *SEE* that environment you'll never know why those tweaks are needed.
Nowhere did I say that the tweaks were not necessary.
Think of it this way. A large organization is probably going to have more than one DBA, probably many. Wouldn't it make sense to split them into specialties such that one group focuses more on logical design and the other on physical issues (performance)?
then you won't be a successful DBA.
Maybe not. It was Ziwethey'ers who suggested I persue that line of work because it was less damaged by OO zealotry. A lot of people seem to get off on performance tweeking, but I would rather focus on maintainability and simplicity of software design from developers' perspectives, not making chips happy.
Maybe I should get a cert in PL/SQL instead? Or, is Java killing that too? Why is everyone copying the spahgetti Sun model? When will the Sun fad die?