[NTLUG:Discuss] OT Perl vs C question

[Fred James]

Chris J Albertson wrote:

>It seems to me that it would be easier, more reliable, and save on disk
>space to access the SQL server directly via PERL, instead of copying the
>SQL result sets into temporary local files. When you read in the files,
>you're going to have to parse the data, eating up cpu cycles. The SQL
>result sets are going to be parsed into columns already, by the nature of
>the RDBMS. PERL::DBI comes to mind here as a solution.
>Flat files are evil. :)
>
>Chris
>
>  
>
Chris Albertson
Admitting that I should not be considered a prize SQL programmer, I have 
relied upon our SQL developers to produce as efficient a query as 
possible.  That said ...

Evil flat files not withstanding, the SQL has been tested and it runs 
for over 24 hours to acquire a 30 days range of data (that test run 
being on a weekend, which is non-peak hours for us).  Our final run must 
collect a 365 days range of data - estimated running time for the SQL 
would therefore be about 304 hours (12.67 days)  We were kind of hoping 
to run this query at least once a week, if not daily.

All sad, but true.
Regards
Fred James

-- 
Compassion alone stands apart from the continuous traffic between good and evil proceeding within us.  "Om Mani Padme Hum"