Re: Loading a Ascii file

On Wed, 21 Aug 2002 18:03:42 GMT, "Peter" <depend3_at_yahoo.com> wrote:

>In general there is nothing wrong with sql*loader, but my boss is not very
>excited about this. The reason is that it is difficult to manage an xls file
>for example.

That is a matter of perception. As soon as you get used to SQL*Loader, using an xls file would be your last choice.

> It would be easier if there would be a direct interface. And
>also sql*loader is not very handy when the databases of origin differ to
>much (for example to import old data in a new remodeled database).

A temp table would handle this with ease. I have done that before, and it work really well.

> I think you can save a lot of money if you can make a good utility that can do this
>in a more intuitive manner.

Define intuitive. Should the program "figure out" which columns go where? I was doing imports (through Access) quite a bit, and we kept getting files from different people. Everyone had their own format. I couldn't write an intuitive program for it. I had to manually edit each file before doing an import. So, I'd load it up in Access move things around, and spit it out.

Brian Received on Thu Aug 22 2002 - 17:18:18 CEST