Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Stored Procedures - Java VS PL/SQL

Status
Not open for further replies.

SprintFlunky

Programmer
Apr 6, 2004
51
US
What is the better approach.

I am starting a new project where my team gets to create a Data Warehouse database that will be called by various server applications to retrieve data. The database will end up being a 100+ tables due to the DBA's normalizing the structures and I don't want the users to have to navigate through that mess to get to the data.

The front end (loading) of the data is a straight forward Shell script and Java code from the source applications (we are just providing a central place to get the data). We do a lot of this today in our existing DW database, but since this is a new project and a new database, I am looking into upgrading our existing approach.

I am planning on creating an API layer that the applications call to retreive the data. In some cases the "API" will be nothing more than a view, but in others, I will be required to program functionality to prevent unauthorized access, bad data, etc.

For the program API's, I am planning on using JAVA stored procedures, however, I want to make sure that is the right choice. What are the advantages of JAVA SP's vs. PL/SQL vs. Java Bean's.

Can anyone tell me the pitfalls and/or advantages to any of these approaches, or sugest a different one.

Thanks in advance.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top