Hi Janet,
In general:
- Reusability: If you have multiple applications accessing the system,
you can reuse the objects already present on the database.
- Naming Standards: (are a must if you decide to use stored procedures)
IE...if the application changes standards, you'll want to know which objects
need to be modified.
- Error handling and exceptions: (Can be handled either way) via the
application and/or the database. Different types of errors exist.
- I/O: stored procedures may cut down on the I/O...depending on the app
- Data Integrity: this is usually handled by the triggers (N/A)
- Flexibility/Maintainence: which will be easier to maintain in the long
term after you've moved on. The code in the application or on the database?
- Misc: Security, ability to tune SP, visibility of RDBMS logic
- "Garbage in / Garbage out"
- "transactions" are easily maintained within the RDBMS
envirionment...after all, that's what they were designed for, right?
For the most part, I agree with Krupesha. It can become a nightmare when
data integrity tips towards the application sides vs. the RDBMS. It
"really" depends on what your application does, and how/(what) the
information in the RDBMS database is used (for). Just balance out the
options and go for it!
Hope this helps...
Klint
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 04, 1999 11:10 AM
> To: [EMAIL PROTECTED]
> Subject: [ND] Using Stored procedures for transaction management
>
>
>
>
>
> I'm not used to using stored procedures but recently I was
> looking over some
> one's ND4 code (for an app that talks to Informix 7) and I noticed that
> stored
> procedures were used whenever a series of INSERT/DELETEs needed to be
> executed
> as a transaction. That looked like a smart coding technique to me, and I'd
> like
> to get other opinions.
>
> Do you recommend using SPs like that? Pros/cons?
>
> Thanks!
> Janet
>
>
> _________________________________________________________________________
>
> For help in using, subscribing, and unsubscribing to the discussion
> forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
>
> For dire need help, email: [EMAIL PROTECTED]
>
> _________________________________________________________________________
>
> For help in using, subscribing, and unsubscribing to the discussion
> forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
>
> For dire need help, email: [EMAIL PROTECTED]
>
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
