The entire case here was around the requestor specifying he'd like the data in Excel format (although presumably CSV would also be acceptable). I can't think of many databases which can't export query results to CSV, or indeed many civil servants who are so completely inept with a computer that they couldn't redact information as (or more) easily in Excel than they could with a PDF.
This is pretty much irrelevant as these requests are not going to end up in the hands of a DBA, or anyone with anything approaching direct access to the databases in question.
It's going to end up with someone who has an adversarial relationship with their own IT department as a 'maker of work'. Bureaucracy isn't something these agencies foist on the public, it just as bad if not worse inside.
The request will go up and down through a series of managers, directors and deputies before being put on the schedule for a change control board meeting.
In that meeting, a representative of the database administrators will explain that this request is not only complex, but potentially quite dangerous. He will point out that required data is actually completely accessible via a clunky mainframe interface wrapped in Java.
Some plebe in the receiving office of the request will end up clicking through that Java interface and printing/exporting the requested data one page at a time.
This process will repeat itself until such requests are a weekly if not daily occurrence at which point the plebe might be given a dedicated interface for exporting such requests.
>'...or indeed many civil servants who are so completely inept with a computer that they couldn't redact information as (or more) easily in Excel than they could with a PDF.'
I take it you've not met many civil servants then?
In any case, the mechanics aren't really the issue. It's the game of hot potato behind the scenes and the eschewing of responsibility that takes place at all levels.
I can virtually guarantee that even if all the stars aligned such that someone did obtain and redact a fully electronic copy of such data it would be rejected for release due to the 'unfamiliar' format. Someone in the chain would fear that they couldn't be sure of what they were releasing because it's not in the specific format they're used to.
If you consider perhaps maybe 3-5% of staff are responsible and competent as well and they are bashed down the ladder by the incompetents as they are seen as a threat then you will see how this sort of stuff persists. The incompetents also persist through incestuous promotions (check on your council register how many people in the same family work in the same chain of command) and arse licking.
Most of these departments need the chain pulling like a toilet.
I've never encountered anything quite like it in the private sector apart from one large defence contractor who employed most of the surrounding area for ten miles.
But I really don't think "run a query and export the result" requires the skills and expenses you describe. It wouldn't be in a database in the first place if the government didn't at least occasionally have to run their own queries against it.
Exporting them into another database where they can be manipulated freely is beyond the skills of most database users, and requires an expensive database administrator, who will have to have meetings with the administrator of the original database, which might result in travel requests, expenses...at which point most organizations will invoke the clause in FOIA rules (at least in America) of charging the requestor the reasonable costs of the data retrieval, which in a case like this will be substantial - at least a few thousand. Bear in mind that that FOIA requests are rarely so broad in scope as to justify the release of an entire database; most requests are for a subset of information about particular individuals, timeframes, political administrations or suchlike.
I often dig through stuff like this in PDF format (because I enjoy reading court cases), and while I can't say I like it, if I really need to get the data out I set up some sort of scraping macro. Most people want something in human readable form and I suspect that if they were given an optical disc with an SQL dtabase on it, or even an XML file, they'd complain about the impenetrability of it.
Perhaps you could suggest some good candidates for release formats that met the criteria of being easily accessible/convertible as well as being manipulable and easy to produce.