Hi Anurag,
Best option is to decide this thing at UOW level as writing a SP for each sql stmt is not feasible. If there are a few sql stmt's(that too not heavy performance wise) then you can keep it in code executing at app server. But for more stmt's it is always better to keep the db logic in sp's only.
Main criteria to keep in mind is
Minimise the jdbc calls from appserver to db(Though sometimes the batch execution mode of jdbc can be used). Manipulation of data can be done in the business logic in the appserver later on.
Warm regards,
Praveen Pandey
Choose a job you love, and you will never have to work a day in your life
-----Original Message-----
From: kumaranurag [mailto:db2udbdba-ezmlmshield-x84270602.[Email address protected]
Sent: Wednesday, November 23, 2005 9:47 AM
To: LazyDBA Discussion
Subject: Design Consideration??
Hi,
Posting this question on my friend's behalf
________________________________________________________________________
Question:
Let us say I have a SQLJ Java application and there is ¹unit of work
that does 50,000 SELECT statements, and 10,000 INSERT statements.
I need to determine if the unit of work (UOW) should be performed using
code executing on the application server (WebSphere Application Server)
, or should it be executing code on the database server, using a stored
procedure.
I would be interested in knowing how others have dealt with this
architectural decision. ¹Do you make a high level decision that
dictates where the database access logic resides ? Or Do you make the
decision as per the UOW requirement ? ¹ small UOW - application server
will do, large UOW - database server.
Thanks
Anil
________________________________________________________________________
************************************************************
************************************************************
HSBC Software Development (India) Pvt Ltd
HSBC Center Riverside,West Avenue ,
25 B Kalyani Nagar Pune 411 006 INDIA
Telephone: +91 20 26683000
Fax: +91 20 26681030
************************************************************
-----------------------------------------
***********************************************************************
This e-mail is confidential. It may also be legally privileged.
If you are not the addressee you may not copy, forward, disclose
or use any part of it. If you have received this message in error,
please delete it and all copies from your system and notify the
sender immediately by return e-mail.
Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability
for any errors or omissions.
***********************************************************************
DISCLAIMER:
This message contains privileged and confidential information and is intended only for the individual named.If you are not the intended recipient you should not disseminate,distribute,store,print, copy or deliver this message.Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted,corrupted,lost,destroyed,arrive late or incomplete or contain viruses.The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.
DB2 & UDB email list listserv db2-l LazyDBA home page