Re: Total Cost of Ownership

In message <ufmdnTco6-i6zuXd4p2dnA_at_comcast.com>, Laconic2 <laconic2_at_comcast.net> writes
>> Stagnation, inadequate communication among all players, high risk of
>making
>> any change, severe procedures for making changes, application performance
>> including performance issues related to the database, ease of reporting
>> against the database including ease for users to have and maintain a data
>> catalog (so they can "shop" for the data they need); mitigation of
>> client/server & version skew issues, and a bunch more -- these might not
>be
>> the most important -- I'll think more about it.
>
>I've repeatedly sped up SQL queries by factors of ten. And most of the
>time, I've taken a close look at the logic behind the query, before diving
>into optimizing it. I think a lot of bad queries have been written by
>people who just don't understand the data.

Relevant to the TCO question - because of the way Pick stores its data, it's actually damn hard - in a system that was properly designed in the first place - to speed up a Pick query.

And it's also relatively easy to prove that there is very little room for improvement.

Cheers,
Wol

-- 
Anthony W. Youngman - wol at thewolery dot demon dot co dot uk
HEX wondered how much he should tell the Wizards. He felt it would not be a
good idea to burden them with too much input. Hex always thought of his reports
as Lies-to-People.
The Science of Discworld : (c) Terry Pratchett 1999