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

[Steve Cook]

That's an excellent guide Paul and it helps a lot. Now I have one of those
"how long is a piece of string questions"! Our focus is on speed - we're
expecting to receive over 100,000 bookings which at peak periods could mean
our server is very busy and we want to keep the code as streamlined as
possible.

I get the impression that opening temp tables and looping through those is
more costly in terms of server loading than doing a bunch of very simple
inserts. Am I barking up the wrong tree?

Despite Rudy's good advice I'm leaning more on the side that Paul
recommended - partly because it's a technique I already understand (time, as
always, is short), partly because this code will never change architecture
(which is ASP as you rightly guessed) and partly because it *sounds* more
effective to me.

I'm open to being proven wrong ;-)


-------------------------------------
 Cookstour - http://www.cookstour.org
-------------------------------------

> -----Original Message-----
> From: Paul Cowan [mailto:evolt at funkwit.com]
> Sent: den 19 juli 2002 01:18
> To: thelist at lists.evolt.org
> Subject: Re: [thelist] MSSQL, transactions, stored procedures and
> multiple inserts (phew !)
>
<SNIP>
> Personally, I would be inclined to hook the transaction out of
> proc_MakeBooking. If there's an error, return some status code: and
> handle that in proc_MakeLotsOfBookings, or in ADO, with a 'high-level'
> transaction.
>
> Hope this helps: transactions are very powerful, but also alarmingly
> complicated! Good luck.
<SNIP>