Yes, SQL92 was introduced in 9.1B (
http://www.oehive.org/versionhistory ). SQL89 was introduced in version 5.0! and everything between the two is SQL89.
Yes, I suppose the binary dump would allow you to dump the data, but not in a readable form.
That's a seasonably large amount of data. Presumably it matters to someone. I might suggest that merely exporting the data is only part of the problem ... you also need to understand the schema in order to know what that data means and how it connects.
Presumably, this is happening in relation to a move to new software. If so, you not only need to deal with getting the data out of the old system, but getting it into the new one ... and this means having to construct a semantic map between the two systems. There is almost certainly going to be data in the old system that has no corresponding place in the new system and data in the new system for which there is no real source in the old. In both cases, you are going to have to decide what to do to make up a consistent set of new data. My experience ... and I have done this sort of thing rather more than once ... is that you want to start out making as much of this semantic data in the context of the old system because there you have rapid access to the schema structure of the old system. Then, your load programs can finish the job. For example, suppose there is a field in the old system which might have as much as 40 characters in it, but this needs to go into into a field which is only 30 characters., it is a lot better to report on what is not going to fit and fix it from the source system.
Bottom line, this is not a job to hack at ... it is a job for someone with experience and tools.
