07-05-05 10:51 PM
Hello Paul.
BizTalk 2004 does all the mapping in memory by loading the source file into
the DOM for transformation. For that reason, you are limited by what .net
can handle.
Microsoft posted
(http://blogs.msdn.com/biztalk_core_.../28/381700.aspx)
that they will only consider documents under 10 MB as supportable – or
something like that so keep that in mind when designing your solution.
I have mapped items in excess of 500 MB in a Receive Pipelines – just to s
ee
if I could do it. It took several hours but completed. Inside an
Orchestration, the top message size was much less – around 200 MB. This i
s
all subjective to your system resources and other things going on inside you
r
system. I would not recommend mapping messages of this size for a productio
n
solution. I had some nice test servers and nothing else running. The down
side is when things fail they do not fail gracefully
(http://www.geekswithblogs.net/sthom...3/29/27655.aspx).
I would try to break your message up into smaller pieces that can be mapped
easier or look into another transformation tool for the transformations.
This is all changing in 2006. In 2006 BizTalk will chunk the message into
100K pieces (if I remember TechEd correctly). It will not increase
performance any but it will at least enable Microsoft supported large messag
e
transforms.
I have a lot of debatching samples on my website
(http://www.biztalkgurus.com) and a lab that walks you through it for a flat
file document. That is, if you decide you can break up your message into
smaller pieces.
Hope this helps.
Stephen W. Thomas
http://www.biztalkgurus.com
"Paul Somers(MVP)" wrote:
> Hi,
>
> I have some Large messages, and I wish to transform them, does anyone know
> the memory implications, or limit on how big I can go?
>
> Are transforms done all in memory?
>
> Paul
>
>
>
[ Post a follow-up to this message ]
| 
