• The usual problem is trying to follow part 1 of rule #2 (follow users' orders) while only bending rule #1 (i.e. a slight performance impact) when you'd really like to break rule #3 (i.e. kill the user who is making a request for a 'tiny change' which requires a major redesign of the database).

    Actually, to be closer to the Laws of Robotics, rule #3 should be

    3. A DBA must protect his own job as long as this does not conflict with rules #1 or #2.

    Of course, we assume that the 'orders' only relate to things done to databases.

    Derek