Well, if you use stored procs then you get better performance with MS
SQL. You also get the ability to change the stored proc without having to
modify source code, as long as the input parameters stay constant.
Some other DBs don't support stored procedures, so you have to weigh that
against it... but its always easy enough to put the SQL into the code later
if thats what you decide to do.
Basically, I say there is no reason why you shouldn't use stored procs if
you're using SQL, even if you think you might be moving to Oracle or
something a couple years down the road.
Anyone know any major reason why its bad that I missed?
___
Michael Dinsmore
Sr. Engineer & Architect
Passkey.com, Inc.
mailto:[EMAIL PROTECTED]
phone:617.328.4800 x230
-----Original Message-----
From: Brian Burridge [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 07, 1999 10:47 AM
To: [EMAIL PROTECTED]
Subject: [JSP-INTEREST] JSP & SQL Stores Procedures
I just wanted to get some of your opinions on this. We are having an
internal discussion about whether or not to use stored procedures for
our SQL, or to put the SQL in the bean or JSP page.
Does anyone have any recommendations either way? Suggestions?
Brian N. Burridge
Web Analyst
Cox Target Media
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
