> If there are more then perhaps we'll build another
> poll to see. But then we need some ready-made answers. I know already
> two: 1. Performance 2. Is not worth bother - I know how to do it by
> hand. (but this one I put it already inside...)
>
> Someone knows other reasons?

Well we are being asked to respond without hearing both cases. Perhaps
(before doing the poll) the question could be raised, something like:

"We propose a feature where the statistics for a database will be
automatically recalculated periodically for writable databases. The
frequency and timing of the updates can be configured (including a
'NEVER' option). The defaults would be [once per week starting Sunday
at 2am/every 5000 transactions/whatever the parameters].

We realise this feature is not for everyone, which is why there is a
NEVER option, but if anyone can still see specific problems with this
feature, could you please detail these."

Note the assumptions I made in the above paragraphs. I do not know the
details yet I am asked how I feel about it. Firebird is designed to
not require a DBA, and it is a feature that fits that model quite
well. I am very interested in the 4 'against it' responses to the
poll, because if they have good reasons, it may cause me to change my
mind (which for the record is 'nice but can live without').

On the performance front, I wrote a SP to update all statistics and
ran it on a specific live database to fix a problem where a particular
screen was taking too long to retrieve the data (because it was using
a bad plan).

With 80MB and ~450 indices, it took under a second on the high spec
server. It was only a couple of seconds on my laptop for the same
database.

Just my 2c
Adam