Re: Cheaper option
That depends on being able to express the required permissions in simple rules and/or lookups, and the system being setup to allow arbitrary queries to run on it.
If it turns out that temp staff aren't allowed to work with fruit unless they're in Reading or have permission from a manager (see paper documentation in box #45C), then SQL may just make a lot of mistake really quickly.
If the software was designed to have a shiny front end and permit NO ONE to have direct access to the tables (secure, innit), then maybe no one could run that SQL (or those that could, well, quoted a ridiculous charge and 4 months to implement).
Biting the hand that feeds IT
