[thelist] MSSQL, transactions, stored procedures and multiple inserts (phew !)

rudy r937 at interlog.com
Thu Jul 18 19:49:01 CDT 2002


what a fabulous post, paul

that's a real keeper

funny, too -- "there are some things I happily admit I just don't get about
SQL Server, and that's one"

as for the design, steve, i would recommend you set it up so that the
database can be called by any scripting language, and not make it reliant
on asp or ado or net or whatever the tla-of-the-month is

stored procs are defined as "persistent stored modules" in an addendum to
sql-92,  and became part of the sql-3 standard later on (i just copied that
straight out of my sql textbook here)

oracle pl/sql and microsoft transact-sql are examples of sql/psm, but i
cannot tell you how closely they follow the standard

in sql/psm you use DECLARE, IF, CASE, LOOP, BEGIN/END, WHILE, etc.,

i would not even worry about whether your stored proc is
standards-compliant, though, because if you ever have to move it,
it will probably be portable (i.e. you will be able to port it, with some
editing perhaps).... UNLESS you have written it to be totally dependent on
some mystical stuff happening on the script side

i guess i shouldn't slam that technology because i really don't know
anything about it -- maybe i'm just naturally skeptical of microsoft
flim-flammery on principle


rudy






More information about the thelist mailing list