Path: news.easynews.com!newsfeed1.easynews.com!easynews.com!easynews!news-out.cwix.com!newsfeed.cwix.com!ctb-nntp1.saix.net!not-for-mail
From: Billy Verreynne <vslabs@onwe.co.za>
Newsgroups: comp.databases.oracle.server
Subject: Flat File Processing
Date: Thu, 10 Oct 2002 12:18:01 +0200
Organization: Verreynne Software Labs
Lines: 13
Message-ID: <ao3k7a$h3r$1@ctb-nnrp2.saix.net>
NNTP-Posting-Host: 198.54.202.209
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
X-Trace: ctb-nnrp2.saix.net 1034245162 17531 198.54.202.209 (10 Oct 2002 10:19:22 GMT)
X-Complaints-To: abuse@saix.net
NNTP-Posting-Date: 10 Oct 2002 10:19:22 GMT
User-Agent: KNode/0.7.1
Xref: newsfeed1.easynews.com comp.databases.oracle.server:163702
X-Received-Date: Thu, 10 Oct 2002 03:19:19 MST (news.easynews.com)

Oracle 8.1.x and later on HP-UX/Linux/Solaris..

How effective is UTL file ito of performance? If having the choice between 
doing flat file processing either via Pro*C, or via PL/SQL using UTL file, 
what would you choose and why? (pretend that SQL*Loader is not an option 
and that db access is a requirement as part of the processing).

Basically what I would like to know if anyone has done some serious 
intensive file processing via PL/SQL and if one should consider this as an 
option instead of using Pro*C.

--
Billy
