Re: De-Normalized output to CSV

Why not just query as joins, then output the query into CSV format? For instance, if you have TableA, TableB, and TableC, and they all get joined together, then run the following query:

SELECT ......
FROM TableA a, TableB b, TableC c
WHERE a.somecolumn=b.somecolumn
AND b.somecolumn=c.somecolumn;

It is now de-normalized and you should have no problems converting to CSV format.

HTH,
Brian

Mark D Powell wrote:
>
> "Allen Gibbons" <agibbons_at_ec.rr.com> wrote in message news:<840_9.753$hG6.66598_at_twister.southeast.rr.com>...
> > I have been asked to extract data from a set of about 100 Oracle
> > database tables and output it into comma delimited files. However,
> > the data should NOT reveal any of the data structure within the
> > database (ie, no normalization).
> >
> > Has anyone out there had to do something like this before?
> >
> > Ideas would be much appreciated.
>
> If you have to produce a csv per table then you are giving away a lot
> of information though the column names, exact lengths, and table
> relationship data is not specified so it really comes down to what
> does, 'NOT reveal any of the data structure within the database" mean.
>
> In some of your cases you might be able to create views that
> denormalize the row structure and create the output file from the view
> instead of from the base tables.
>
> For help with comma delimited files see the cooperative FAQ article:
> How do I export a database table to a flat file? To a comma or other
> character delimited file ?
>
> HTH -- Mark D Powell --
>
> http://www.jlcomp.demon.co.uk/faq/flatfile.html
Received on Thu Jan 30 2003 - 09:56:20 CST