Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

A colleague claims BizTalk is slow and should not be used. He argues that he has never heard anything positive about BizTalk, that it is slow and that customers using it wants to replace it with something else.

I'm in the planning phase of some datamigration and I wonder if more people feel this way. I find it a bit hard to believe that it should not work properly.

I'm looking into using BizTalk for nightly updating a few million records in Dynamics CRM instead of writing a custom app.

share|improve this question

closed as not constructive by ThatGraemeGuy, joeqwerty, pauska, Zypher Dec 14 '11 at 17:47

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

define "slow"... – Bart Silverstrim Dec 14 '11 at 13:00
He said "2-3 seconds delay when sending a message from client to somewhere", but in this case he was arguing for the scenario above. It was vague, hence my general question. – Tedd Hansen Dec 14 '11 at 14:19
two or three seconds is slow? – Bart Silverstrim Dec 14 '11 at 14:20
Ask your colleague how many black swans he has seen lately. Just because he has not heard anything positive doesn't mean there isn't positive press and positive results from using BizTalk. – Top__Hat Dec 14 '11 at 15:01
Well, thats kind of why I posted the question. :) – Tedd Hansen Dec 15 '11 at 20:46

BizTalk is very high performance when it comes to throuhgput (messages per second). Latency (time per individual message) is not as high performance, but should be suitable for 90% of scenarios.

However, for a data migration there are much better tools out there, such as SSIS on the microsoft sql stack. BizTalk is about moving small data in real time, not moving large data in a one off

share|improve this answer
SSIS doesn't seem right for moving data from Windows Message Queue to Dynamics CRM HTTP REST. – Tedd Hansen Dec 14 '11 at 14:17

I will agree with Hugh on this - Biztalk is very fast if the architecture is correct. You can scale it out and up (since it uses SQL server as the messagebox).

Every time I have seen a "slow" biztalk it is typically the design of the orchestration and a failure to understand the implications of the messagebox.

In terms of a data migration for nightly updates to records using CRM Webservices - if you are just updating programmatically, Biztalk will not really get you any benefits and will cost you time.

A SSIS really will be better. Data Integration/Migration using SQL Integration Services (SSIS) 2008 MSDN BLOG

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.