I Don't know if I'd call this method the simplest, each output file can only be imported into one specific table and only those columns named. It also requires that the exporter must know the table name and field names prior to exporting.
While I'll agree, it is most like the fastest for importing into a database, and easiest for importing, but I would think that using an insert into based on a select of an external file in comma delimited format would also be just easy on import, and a lot easier to export, since you could include many fields in the external file, and just select those that you want to insert. You could have one long flattened export data line, and setup multiple inserts off the same external file, only selecting different columns in the sub select. I havn't used SQLserver too much for external files, so I'm assuming it's as easy to setup as using Oracle for external files. George > -----Original Message----- > From: [email protected] [mailto:u2-users- > [email protected]] On Behalf Of Tony Gravagno > Sent: Wednesday, January 20, 2010 5:43 PM > To: [email protected] > Subject: Re: [U2] Export files > > > When someone asks the "simplest" way to do things, consider just > creating text files that have SQL queries. Then shell out to > execute them or transfer them to a system where you can do so and > execute them elsewhere. > > INSERT INTO table_name (column1, column2, column3,...) > VALUES (value1, value2, value3,...) > > > Tony Gravagno > Nebula Research and Development > TG@ remove.pleaseNebula-RnD.com > Nebula R&D provides Pick/MultiValue development services > remove.pleaseNebula-RnD.com/blog > Visit PickWiki.com! Contribute! > http://Twitter.com/TonyGravagno > _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
