I'm thinking of a system with very high volume, tens of thousands of transactions being sent in batches of 1,000 to eConnect in XML using the eConnect schema. Where is the bottle-neck for processing transactions via eConnect?
Could you gain an advantage by installing the eConnect service on additional machines and distributing the batches across them? Or is the bottle-neck at the SQL Server level?