alistairbayley
We also had a problem where user queries that return too many columns cause the DB server process to OOM. And then it restarts, so another 20 mins of downtime. Also not cool.
We liked the tagging and rollup features, and automatic retention management, but those first 2 problems really turned us off.
A given individual may not have much control over whether or not they get sick, but then can influence whether or not they share that illness with their colleagues. The individual allowance has a stronger incentive to return to work vs the pool, because there is no cost to the individual if their colleagues become ill. With a pooled allowance, there is a cost to the individual if they make their colleagues ill.
2. Why place some predicates in the where-clause and others in the join-clauses? What's the thinking here? Why not put all predicates up in the join-clauses, nearer to the tables that they affect?
Especially as it's just a re-badged Sybase...
But I've never had to use it, so I am just guessing.
Same article, different site: https://communities.bmc.com/docs/DOC-9902
And a paper: http://www.sigmod.org/publications/sigmod-record/0506/p47-ar...
Here's a comparison of the different approaches in a matrix: http://vadimtropashko.wordpress.com/2008/08/09/one-more-nest...