Re: SQL or Java?

[Quoted] I think the big question that you need to answer is this: do you NEED the relational capabilities of an RDBMS to perform these "field checks" and data merges? Unless you don't, IMHO, the DBA just doesn't want to administer [Quoted] the separate database for these conversions and is looking to push this out of [Quoted] his realm of responsibility.

In article <3c45e547$0$43571$272ea4a1_at_news.execpc.com>, "AmoroSSo" <pacomoy_at_yahoo.com> wrote:
>I am working in a project were we need to move a lot of data (100 Million
>records a year) into Oracle (8i).
>We have a Java program (EJB) that does the file and record integrity checks
>and loads the data into three Oracle tables.
>
>Then we run a set of SQL stored procedures to check the integrity and
>validity of the individual fields and store the results in yet another
>table. We believe this process could not be done with the original files,
>since they are just plain text files.
>
>The forth table is then use to create a report that will help the people
>that submitted the data for cleaning purposes, so they can send it again
>(and re-load it into the database). This process goes on until the data is
>as clean as possible. At that point the data in the original three tables is
>moved and converted to another database that will be used for reporting.
>
>This other database is normalized and read only.
>
>The DBA is telling us that we shouldn't use Oracle to do this checking (nor
>the moving to the final database), but an external application like Java or
>C++. Our opinion is that it would be faster, and less intensive for the
>network and the database, to do it in Oracle using PL/SQL.
>
>So the question is ... who is right? or how can I find information or
>benchmarks on this topic.
Received on Wed Jan 16 2002 - 22:17:56 CET