RE: Update/Insert into SQL
From: Neal Walters (NealWalters_at_discussions.microsoft.com)
Date: 01/26/05
- Next message: Nirav Parekh: "Foriegn Character in XML causing the maps to fail."
- Previous message: Stephen W. Thomas: "RE: scripting functoid with optional inputs"
- In reply to: Ronnie Swafford: "Update/Insert into SQL"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 26 Jan 2005 14:53:03 -0800
Just write an SQL Stored Procedure to handle the problem. It could check to
see if row exists, update if it exists, or add it if it doesn't exist.
When you run the SQL adapter from Visual Studio, it will build a schema
called something like SqlService.xsd. You can rename it to something more
meaningful. You can then map your data to this schema. The SqlAdapter also
build a "dummy" orchestration which you can delete.
All the parms of the stored procedure will be exposed as attributes in the
schema. If the stored procedure returns a table, the table and elements will
also be in the schema. The SQL adapter will ask for a Request and Response
root element name. The Request root element name will wrap the stored
procedure parms, and the Response root element name will wrap any returned
data.
I don't know if you are using orchestration or not, but you would create a
Request/Response port (not sure if a Send-Only port would work). I still
haven't figured out how to get the return-code from a Stored Proc back into
Biztalk.
Neal Walters
http://Biztalk-Training.com
- Next message: Nirav Parekh: "Foriegn Character in XML causing the maps to fail."
- Previous message: Stephen W. Thomas: "RE: scripting functoid with optional inputs"
- In reply to: Ronnie Swafford: "Update/Insert into SQL"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
