Brandon,

Stored procedures are always faster than connecing to a database, preparing
a transaction, inserting, closing, etc.  You save a minimum of 4 RPC calls
in the client-server envrionment (depending on how integrated the procedure
language is with the database engine - some pl's are just bolt ons after the
fact).

PSM96 is the partitioning of the SQL92 RFC that deals with stored
procedures.  Check out the RFC or the book "understanding slq's stored
procedure: SQL/PSM" by Jim Melton.

Regarding examples, check out our database product, Virtuoso - it's entire
admin interface is built with stored procedures delivering dynamically
generated webpages (and allowing inserts, etc.) and we fully support SQL92
and PSM96  http://www.openlinksw.com/virtuoso  You can view the stored
procedures as well as alter them at will.  Plus, it's a free download that
doesn't expire, and has no limit on functionality (except to limit the free
copy to 3 concurrent database sessions - but you wouldn't need more for
development or an internal use).

Hope this helps.

Best regards,
Andrew


-----Original Message-----
From: Brandon Duncan [mailto:bduncan@p...]
Sent: Wednesday, July 05, 2000 12:00 AM
To: sql language
Subject: [sql_language] RE: Stored procudures for INSERT commands


Mr. Hill,

Sorry, I forgot something in the last response I sent.  Do you think doing
Inserts via a stored procedure would be faster than using the
ADODB.Connection.BeginTrans/CommitTrans method for insert data?  That's the
key to my question, what's the fastest way to get information into the
database?

Thanks again,

Brandon

---
Wrox Professional Wireless Developer Conference, Amsterdam, July 10-12.
Covering application of WAP, XML, ASP, Java and C++ to wireless computing,
choose from 40+ technical sessions delivered by industry experts:
http://www.wroxconferences.com/ConferenceHome.asp?ConfID=9