Hi,

<gs class="GINGER_SOFTWARE_mark" ginger_software_uiphraseguid="b62d5439-db3c-4cd5-a208-e8179d8f8d41" id="e66726d5-cbf2-407b-ab1d-c28a98353fbe">Scenario</gs> I:  Biztalk 2006 R2 running on OS 2003

Scenario II: Biztalk 2013 running on OS 2012

I am sure that comparing these two scenarios are like comparing an old Vokswagen with a new BMW.

In terms of scalability and performance what is the difference?

<gs class="GINGER_SOFTWARE_mark" ginger_software_uiphraseguid="6b64761b-125c-424e-98ee-a002819fde03" id="13a95b6f-549d-44f3-8aba-7feccefa6a2c">On</gs> my workplace we have dozens of projects running in production implemented in Scenario I, we are <gs class="GINGER_SOFTWARE_mark" ginger_software_uiphraseguid="6b64761b-125c-424e-98ee-a002819fde03" id="23f8ed6d-09f0-4e78-9a2f-3480fbba0b18">weighting</gs> to move to II, but I need economic motives. (<gs class="GINGER_SOFTWARE_mark" ginger_software_uiphraseguid="b42e9ef7-fb62-4fa9-8894-44599c0b1de3" id="44c303b4-cea1-4f1c-9cd7-41c07f0399fb">like</gs> e.g. <gs class="GINGER_SOFTWARE_mark" ginger_software_uiphraseguid="81763200-06dd-48e5-887e-203518c0b236" id="0111a3aa-b33f-440a-9729-0b6a6e10450e">if</gs> we double the <gs class="GINGER_SOFTWARE_mark" ginger_software_uiphraseguid="81763200-06dd-48e5-887e-203518c0b236" id="058f7018-daca-4503-92ab-cbc481d132a5">work load</gs>, <gs class="GINGER_SOFTWARE_mark" ginger_software_uiphraseguid="81763200-06dd-48e5-887e-203518c0b236" id="8a0de223-9b1e-400c-9754-f3ec32f80cc4">scenario</gs> I <gs class="GINGER_SOFTWARE_mark" ginger_software_uiphraseguid="81763200-06dd-48e5-887e-203518c0b236" id="63dfae7e-4e8c-4225-8049-51b8d7bb378b">is</gs> unable to scale)

Thanks

            Daniel

HI Daniel ,

There are much of performance gain with new OS and Biz Talk 2013  .On solution prospective The execution time of mapper will be less on newer version due to xslt compiled transform instead of xslt transform .

With BizTalk 2013 or newer version you have centralized exception Management Portal , ESB toolkit ,WCF Line of business adapters and connectors to the cloud .

These are really a pathway to define future integration framework .In meanwhile you also need to look for MS support for the BizTalk 2006R2 and windows server 2003 .

BizTalk 2013 and later version is being supported over cloud and the development time required is very less compared to earlier version ..

There are lot of documents and blog exists which will guide you the benefits of newer version of BizTalk

http://blogs.biztalk360.com/reasons-for-moving-from-biztalk-server-2006-to-biztalk-server-newer version

decision about whether we should choose BizTalk 2010 or BizTalk 2013 for this project

Reasons to Move On with BizTalk 2013

Thanks
Abhishek

• Edited by Abhishek0127[Abhishek kumar]MVP 2 hours 34 minutes ago
• Proposed as answer by Maheshkumar S TiwariMVP 1 hour 40 minutes ago

The biggest difference is the supportability of BizTalk. Windows Server 2003, SQL Server 2005 and BizTalk Server 2006 R2 are end of support life or there abouts. In case something does go wrong Microsoft may not be able to support you from a fix standpoint.

Secondly, it is likely that you're using physical hardware for your environment that is likely 5 years or more old. So your solution would benefit from a H/W refresh or you might wish to host it now on a Virtual environment thereby saving up on data center real estate (rack space, etc.).

In terms of capability, BizTalk 2013 offers FTP/S, SFTP, REST and other technology enhancements over BizTalk 2006 R2. So if you're building a case for refresh, your strongest justification would come from the operational and support risks to the business for not upgrading. Remember this is not just a version + 1 which you can afford to sit out on.

Regards.

• Proposed as answer by Maheshkumar S TiwariMVP 1 hour 40 minutes ago

HI Daniel ,

There are much of performance gain with new OS and Biz Talk 2013  .On solution prospective The execution time of mapper will be less on newer version due to xslt compiled transform instead of xslt transform .

With BizTalk 2013 or newer version you have centralized exception Management Portal , ESB toolkit ,WCF Line of business adapters and connectors to the cloud .

These are really a pathway to define future integration framework .In meanwhile you also need to look for MS support for the BizTalk 2006R2 and windows server 2003 .

BizTalk 2013 and later version is being supported over cloud and the development time required is very less compared to earlier version ..

There are lot of documents and blog exists which will guide you the benefits of newer version of BizTalk

http://blogs.biztalk360.com/reasons-for-moving-from-biztalk-server-2006-to-biztalk-server-newer version

decision about whether we should choose BizTalk 2010 or BizTalk 2013 for this project

Reasons to Move On with BizTalk 2013

Thanks
Abhishek

• Edited by Abhishek0127[Abhishek kumar]MVP Monday, July 06, 2015 4:31 AM
• Proposed as answer by Maheshkumar S TiwariMVP Monday, July 06, 2015 5:24 AM

HI Daniel ,

There are much of performance gain with new OS and Biz Talk 2013  .On solution prospective The execution time of mapper will be less on newer version due to xslt compiled transform instead of xslt transform .

With BizTalk 2013 or newer version you have centralized exception Management Portal , ESB toolkit ,WCF Line of business adapters and connectors to the cloud .

These are really a pathway to define future integration framework .In meanwhile you also need to look for MS support for the BizTalk 2006R2 and windows server 2003 .

BizTalk 2013 and later version is being supported over cloud and the development time required is very less compared to earlier version ..

There are lot of documents and blog exists which will guide you the benefits of newer version of BizTalk

http://blogs.biztalk360.com/reasons-for-moving-from-biztalk-server-2006-to-biztalk-server-newer version

decision about whether we should choose BizTalk 2010 or BizTalk 2013 for this project

Reasons to Move On with BizTalk 2013

Thanks
Abhishek

• Edited by Abhishek0127[Abhishek kumar]MVP Monday, July 06, 2015 4:31 AM
• Proposed as answer by Maheshkumar S TiwariMVP Monday, July 06, 2015 5:24 AM

HI Daniel ,

There are much of performance gain with new OS and Biz Talk 2013  .On solution prospective The execution time of mapper will be less on newer version due to xslt compiled transform instead of xslt transform .

With BizTalk 2013 or newer version you have centralized exception Management Portal , ESB toolkit ,WCF Line of business adapters and connectors to the cloud .

These are really a pathway to define future integration framework .In meanwhile you also need to look for MS support for the BizTalk 2006R2 and windows server 2003 .

BizTalk 2013 and later version is being supported over cloud and the development time required is very less compared to earlier version ..

There are lot of documents and blog exists which will guide you the benefits of newer version of BizTalk

http://blogs.biztalk360.com/reasons-for-moving-from-biztalk-server-2006-to-biztalk-server-newer version

decision about whether we should choose BizTalk 2010 or BizTalk 2013 for this project

Reasons to Move On with BizTalk 2013

Thanks
Abhishek

• Edited by Abhishek0127[Abhishek kumar]MVP Monday, July 06, 2015 4:31 AM
• Proposed as answer by Maheshkumar S TiwariMVP Monday, July 06, 2015 5:24 AM
• Marked as answer by Angie xuMicrosoft contingent staff, Moderator 1 hour 17 minutes ago

HI Daniel ,

There are much of performance gain with new OS and Biz Talk 2013  .On solution prospective The execution time of mapper will be less on newer version due to xslt compiled transform instead of xslt transform .

With BizTalk 2013 or newer version you have centralized exception Management Portal , ESB toolkit ,WCF Line of business adapters and connectors to the cloud .

These are really a pathway to define future integration framework .In meanwhile you also need to look for MS support for the BizTalk 2006R2 and windows server 2003 .

BizTalk 2013 and later version is being supported over cloud and the development time required is very less compared to earlier version ..

There are lot of documents and blog exists which will guide you the benefits of newer version of BizTalk

http://blogs.biztalk360.com/reasons-for-moving-from-biztalk-server-2006-to-biztalk-server-newer version

decision about whether we should choose BizTalk 2010 or BizTalk 2013 for this project

Reasons to Move On with BizTalk 2013

Thanks
Abhishek

• Edited by Abhishek0127[Abhishek kumar]MVP Monday, July 06, 2015 4:31 AM
• Proposed as answer by Maheshkumar S TiwariMVP Monday, July 06, 2015 5:24 AM
• Marked as answer by Angie xuMicrosoft contingent staff, Moderator Tuesday, July 14, 2015 5:48 AM

HI Daniel ,

There are much of performance gain with new OS and Biz Talk 2013  .On solution prospective The execution time of mapper will be less on newer version due to xslt compiled transform instead of xslt transform .

With BizTalk 2013 or newer version you have centralized exception Management Portal , ESB toolkit ,WCF Line of business adapters and connectors to the cloud .

These are really a pathway to define future integration framework .In meanwhile you also need to look for MS support for the BizTalk 2006R2 and windows server 2003 .

BizTalk 2013 and later version is being supported over cloud and the development time required is very less compared to earlier version ..

There are lot of documents and blog exists which will guide you the benefits of newer version of BizTalk

http://blogs.biztalk360.com/reasons-for-moving-from-biztalk-server-2006-to-biztalk-server-newer version

decision about whether we should choose BizTalk 2010 or BizTalk 2013 for this project

Reasons to Move On with BizTalk 2013

Thanks
Abhishek

• Edited by Abhishek0127[Abhishek kumar]MVP Monday, July 06, 2015 4:31 AM
• Proposed as answer by Maheshkumar S TiwariMVP Monday, July 06, 2015 5:24 AM
• Marked as answer by Angie xuMicrosoft contingent staff, Moderator Tuesday, July 14, 2015 5:48 AM

The biggest difference is the supportability of BizTalk. Windows Server 2003, SQL Server 2005 and BizTalk Server 2006 R2 are end of support life or there abouts. In case something does go wrong Microsoft may not be able to support you from a fix standpoint.

Secondly, it is likely that you're using physical hardware for your environment that is likely 5 years or more old. So your solution would benefit from a H/W refresh or you might wish to host it now on a Virtual environment thereby saving up on data center real estate (rack space, etc.).

In terms of capability, BizTalk 2013 offers FTP/S, SFTP, REST and other technology enhancements over BizTalk 2006 R2. So if you're building a case for refresh, your strongest justification would come from the operational and support risks to the business for not upgrading. Remember this is not just a version + 1 which you can afford to sit out on.

Regards.

• Proposed as answer by Maheshkumar S TiwariMVP Monday, July 06, 2015 5:24 AM

The biggest difference is the supportability of BizTalk. Windows Server 2003, SQL Server 2005 and BizTalk Server 2006 R2 are end of support life or there abouts. In case something does go wrong Microsoft may not be able to support you from a fix standpoint.

Secondly, it is likely that you're using physical hardware for your environment that is likely 5 years or more old. So your solution would benefit from a H/W refresh or you might wish to host it now on a Virtual environment thereby saving up on data center real estate (rack space, etc.).

In terms of capability, BizTalk 2013 offers FTP/S, SFTP, REST and other technology enhancements over BizTalk 2006 R2. So if you're building a case for refresh, your strongest justification would come from the operational and support risks to the business for not upgrading. Remember this is not just a version + 1 which you can afford to sit out on.

Regards.

• Proposed as answer by Maheshkumar S TiwariMVP Monday, July 06, 2015 5:24 AM

The biggest difference is the supportability of BizTalk. Windows Server 2003, SQL Server 2005 and BizTalk Server 2006 R2 are end of support life or there abouts. In case something does go wrong Microsoft may not be able to support you from a fix standpoint.

Secondly, it is likely that you're using physical hardware for your environment that is likely 5 years or more old. So your solution would benefit from a H/W refresh or you might wish to host it now on a Virtual environment thereby saving up on data center real estate (rack space, etc.).

In terms of capability, BizTalk 2013 offers FTP/S, SFTP, REST and other technology enhancements over BizTalk 2006 R2. So if you're building a case for refresh, your strongest justification would come from the operational and support risks to the business for not upgrading. Remember this is not just a version + 1 which you can afford to sit out on.

Regards.

• Proposed as answer by Maheshkumar S TiwariMVP Monday, July 06, 2015 5:24 AM
• Marked as answer by Angie xuMicrosoft contingent staff, Moderator 1 hour 17 minutes ago

The biggest difference is the supportability of BizTalk. Windows Server 2003, SQL Server 2005 and BizTalk Server 2006 R2 are end of support life or there abouts. In case something does go wrong Microsoft may not be able to support you from a fix standpoint.

Secondly, it is likely that you're using physical hardware for your environment that is likely 5 years or more old. So your solution would benefit from a H/W refresh or you might wish to host it now on a Virtual environment thereby saving up on data center real estate (rack space, etc.).

In terms of capability, BizTalk 2013 offers FTP/S, SFTP, REST and other technology enhancements over BizTalk 2006 R2. So if you're building a case for refresh, your strongest justification would come from the operational and support risks to the business for not upgrading. Remember this is not just a version + 1 which you can afford to sit out on.

Regards.

• Proposed as answer by Maheshkumar S TiwariMVP Monday, July 06, 2015 5:24 AM
• Marked as answer by Angie xuMicrosoft contingent staff, Moderator Tuesday, July 14, 2015 5:48 AM

The biggest difference is the supportability of BizTalk. Windows Server 2003, SQL Server 2005 and BizTalk Server 2006 R2 are end of support life or there abouts. In case something does go wrong Microsoft may not be able to support you from a fix standpoint.

Secondly, it is likely that you're using physical hardware for your environment that is likely 5 years or more old. So your solution would benefit from a H/W refresh or you might wish to host it now on a Virtual environment thereby saving up on data center real estate (rack space, etc.).

In terms of capability, BizTalk 2013 offers FTP/S, SFTP, REST and other technology enhancements over BizTalk 2006 R2. So if you're building a case for refresh, your strongest justification would come from the operational and support risks to the business for not upgrading. Remember this is not just a version + 1 which you can afford to sit out on.

Regards.

• Proposed as answer by Maheshkumar S TiwariMVP Monday, July 06, 2015 5:24 AM
• Marked as answer by Angie xuMicrosoft contingent staff, Moderator Tuesday, July 14, 2015 5:48 AM