Re: Sql adapter using SP - insert parent-child with a nextnumber-key
- From: Dan Rosanova <dnova7@xxxxxxxxx>
- Date: Wed, 19 Nov 2008 07:54:05 -0800 (PST)
Well first I'd like to say good work on part one. I would advise you
do this without making multiple round trips to the SQL Adapter. I
assume your calls right now are batched and sent as one message (which
they should be).
I know one way I’ve gotten around this exact same problem was to
simply send the xml to one stored procedure and use OPENXML within SQL
Server to flatten it into tables (and call other SPs / Functions).
This would effectively be putting a controller into the process in the
form of a stored procedure.
Otherwise you could make the call to get the Next Number before you
send this batch of SQL commands and use the result (assigned in a map
or something) to prepare your insert message. Be sure to reuse the
same port if you end up making the second call. The wizard always
wants to create a new one.
Kind Regards,
-Dan
.
- Follow-Ups:
- Re: Sql adapter using SP - insert parent-child with a nextnumber-k
- From: isabelledc
- Re: Sql adapter using SP - insert parent-child with a nextnumber-k
- References:
- Sql adapter using SP - insert parent-child with a nextnumber-key
- From: isabelledc
- Sql adapter using SP - insert parent-child with a nextnumber-key
- Prev by Date: Sql adapter using SP - insert parent-child with a nextnumber-key
- Next by Date: Re: One message should result into inserts into several sql-tables
- Previous by thread: Sql adapter using SP - insert parent-child with a nextnumber-key
- Next by thread: Re: Sql adapter using SP - insert parent-child with a nextnumber-k
- Index(es):
Relevant Pages
|
