Why not combine BizTalk into SSIS ?
-
Saturday, November 01, 2008 5:03 AM
As we knew, SSIS is so powerful, and many overlap with BizTalk, so why not combine BIzTalk into SSIS except business consideration ?
Answers
-
Sunday, November 02, 2008 1:10 PM
Hi Keith Liu,
I think you have to know that SSIS is designed to move and manipulate very large amount of data over extremely high performance batch processing where BizTalk has been designed to move, process, vaidate, transform, and route low rate of transactions consisting of tiny amounts of business data, also BizTalk engine works with the xml data, so we have always to convert any type of data to an xml so BizTalk can work with.
I think if you are working with critical business data then you should go with the BizTalk, while SSIS is fit to move the data between databases, and/or moving the data between SQL database and other datasources.
As conclusion and in my opinion, I don’t find any benefit to combine BizTalk and SSIS. But I think that some features of the BizTalk can be built over the SSIS.
Thanks,
-Firas
All Replies
-
Saturday, November 01, 2008 9:12 AMAnswererAlthough the line can get blurry with some projects, both are very different systems built differently and are usually meant for different scenarios: SSIS for ETL, batch processing, large amounts of data. BizTalk for smaller files, real time processing, business rules, business process management...
I guess it would be nice though to have both combined into one! But I don't think it's only a matter of business consideration and I don't see it happening anytime soon.
-
Saturday, November 01, 2008 4:34 PM
Hi
SSIS i used to merge the data. and BizTalk is used to setup a SOA platform. BizTalk can know the mean of the message and where to go.
SSIS is a one feature of SQL Server. but BizTalk is a MS Server production.
-
Saturday, November 01, 2008 9:19 PMModerator
In the future of the Microsoft platform with Windows Azure you have SQL Data Services which enables an even more SOA-like version of SQL Server. So in some ways a few of the BizTalk SOA features will end up appearing in the SQL Data Services (SDS). Here is a link to an overview of SDS this: http://msdn.microsoft.com/en-us/library/cc512402.aspx.
But for now it is helpful to recognize that these are different products and are ideally targeted at different implementation scenarios.
Thanks,
-
Sunday, November 02, 2008 3:08 AM
So, merge together is the trend ? right?
-
Sunday, November 02, 2008 1:10 PM
Hi Keith Liu,
I think you have to know that SSIS is designed to move and manipulate very large amount of data over extremely high performance batch processing where BizTalk has been designed to move, process, vaidate, transform, and route low rate of transactions consisting of tiny amounts of business data, also BizTalk engine works with the xml data, so we have always to convert any type of data to an xml so BizTalk can work with.
I think if you are working with critical business data then you should go with the BizTalk, while SSIS is fit to move the data between databases, and/or moving the data between SQL database and other datasources.
As conclusion and in my opinion, I don’t find any benefit to combine BizTalk and SSIS. But I think that some features of the BizTalk can be built over the SSIS.
Thanks,
-Firas

