SQL send port per updategram in an orchestration?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Xerox (Xerox_at_discussions.microsoft.com)
Date: 11/08/04 

Date: Mon, 8 Nov 2004 02:06:08 -0800

Looking at the way SQL send ports are configured (the fact that they need a
target schema definition specified) it looks like that one of these send
ports is required for every updategram/service used within an orchestration
that uses a different schema.

Is that correct? Can the same SQL send port be used for different updategram
schemas?

Relevant Pages

  • RE: Side-by-Side Deployment Issue
    ... Then enlist and start the new orchestration ... >pipeline for the SQL adapter. ... >only a specific version number of the schema. ... As my ports are late-bound, ...
    (microsoft.public.biztalk.general)
  • Re: SQL send port per updategram in an orchestration?
    ... > ports is required for every updategram/service used within an orchestration ... > that uses a different schema. ... The same SQL Send Port can be used for all SQL related processing. ...
    (microsoft.public.biztalk.general)
  • SQL Adapter Disassembling Result Sets & Dynamic Parameters
    ... properties of the schema returned in my orchestration. ... Also after processing all the records returned by SQL adapter in my ... from the toolbox drag an xml disassembler ...
    (microsoft.public.biztalk.general)
  • SQL Adapter Disassembling Result Sets & Dynamic Parameters
    ... properties of the schema returned in my orchestration. ... Also after processing all the records returned by SQL adapter in my ... from the toolbox drag an xml disassembler ...
    (microsoft.public.biztalk.server)
  • Re: SQL Server
    ... >> SQL Service manager shows that \\LAPTOP\PALSOFT - MSSQLServer is running. ... Antivirus is Sophos ... > allows you to check connectivity to ports. ... And it looks like you can in fact get the server manger status ...
    (uk.rec.motorcycles)