RE: Why use Pro*C for spooling result sets to flat files when you can do the same thing in SQL*Plus?
- From: "Bellows, Bambi (Comsys)" <bbel5@xxxxxxxxxxxx>
- To: <jpiwowar@xxxxxxxxx>, <bwmyers@xxxxxxxxx>
- Date: Thu, 2 Sep 2010 09:30:02 -0500
If there are complex procedural things to do, sometimes a 3GL is needed. But,
I tend to agree with John; your guy probably just used the tool he was most
comfortable with.
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx on behalf of John Piwowar
Sent: Wed 9/1/2010 5:48 PM
To: bwmyers@xxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: Why use Pro*C for spooling result sets to flat files when you can
do the same thing in SQL*Plus?
Likely reason: speed
Likely unspoken reason: "job security"
There may be other reasons that make sense for your company's applications
architecture and institutional preferences. The unwillingness to help the "new
guy" get up to speed by explaining those reasons, however, speaks volumes. :-P
Regards,
John P.
On Wed, Sep 1, 2010 at 3:23 PM, Bill Myers <bwmyers@xxxxxxxxx> wrote:
In my previous post,
//www.freelists.org/post/oracle-l/Any-valid-security-concerns-using-Data-Pump-over-conventional-expimp,
I mentioned that the DBAs at my new job use Pro*C to export data to flat
files. So I asked one of them in a meeting: "why not use SQL*Plus instead?"
Response after a long awkward stare: "you tell me". I have searched the forums
and docs to no avail (besides maybe some speed advantage).
So, is there any real advantage to using Pro*C over SQL*Plus to spool
result sets to flat files? I certainly don't want to become a Pro*C expert, so
any ideas would be greatly appreciated.
Thanks in advance.
Bill
9i OCA/10g OCP DBA
Other related posts:
