tag:blogger.com,1999:blog-19890711.post7971713905458349273..comments2023-10-14T19:50:07.705+10:00Comments on Marcus Rosen.NET: SQL Server 2005 Integration Service (SSIS) vs. BizTalk Server 2006 (Updated)Marcus Rosenhttp://www.blogger.com/profile/05678723267559173458noreply@blogger.comBlogger10125tag:blogger.com,1999:blog-19890711.post-47056790105757441172014-04-01T17:54:18.017+10:002014-04-01T17:54:18.017+10:00I am impressed by the quality of information on th...I am impressed by the quality of information on this website. There are a lot of good resources here. Thanks for sharing !digital certificatehttp://www.arx.com/information/digital-certificatenoreply@blogger.comtag:blogger.com,1999:blog-19890711.post-50669549894949238682009-03-11T09:28:00.000+10:002009-03-11T09:28:00.000+10:00Clearly BizTalk is a generally a more expensive so...Clearly BizTalk is a generally a more expensive solution than SSIS, there is no arguments there. <BR/><BR/>What the original post was trying to high-light was where the abilities of each platform overlap. As stated my background is in BizTalk which is why I welcome comments like yours. <BR/><BR/>I guess the bottom line is if you want to do data or file level integration use SSIS and if you need to do more business process level integration use BizTalk (if feasible).Marcus Rosenhttps://www.blogger.com/profile/05678723267559173458noreply@blogger.comtag:blogger.com,1999:blog-19890711.post-88431498771494340932009-03-11T08:23:00.000+10:002009-03-11T08:23:00.000+10:00Marcus,As far as I know there will be some custom ...Marcus,<BR/><BR/>As far as I know there will be some custom code involved to handle OS-level events, however there is a huge elephant here that nobody is addressing, and that is cost. There is a huge difference in cost between SSIS and Biztalk, so from that perspective writing some custom components might be well worth it.Unknownhttps://www.blogger.com/profile/03638746140808263752noreply@blogger.comtag:blogger.com,1999:blog-19890711.post-2385564792831946052009-03-11T05:31:00.001+10:002009-03-11T05:31:00.001+10:00This comment has been removed by the author.Marcus Rosenhttps://www.blogger.com/profile/05678723267559173458noreply@blogger.comtag:blogger.com,1999:blog-19890711.post-80664699524285693282009-03-11T05:31:00.000+10:002009-03-11T05:31:00.000+10:00Emad, Is this an out of the box feature of SSIS? O...Emad, Is this an out of the box feature of SSIS? Or does it involve custom code like hooking into WMI or using a FileWatcher?Marcus Rosenhttps://www.blogger.com/profile/05678723267559173458noreply@blogger.comtag:blogger.com,1999:blog-19890711.post-38784108442873509922009-03-11T04:52:00.000+10:002009-03-11T04:52:00.000+10:00In the first scenario "File Order Batch", you say ...In the first scenario "File Order Batch", you say that SSIS is more suitable for processing files on a scheduled basis but not when the files are created. My shallow understanding so far of SSIS is that in can monitor and handle OS-level events which I interpret as being able to process a file at the time it's created, yes?Unknownhttps://www.blogger.com/profile/03638746140808263752noreply@blogger.comtag:blogger.com,1999:blog-19890711.post-90771302497025723612009-02-24T05:12:00.000+10:002009-02-24T05:12:00.000+10:00useful points. However, one clarification about th...useful points. However, one clarification about the Biztalk messages. They do not have to be XML. You can pass any binary format message as well through the biztalk engine when you use pass through pipelines as you dont need to know anything about the message for those pipelines, but if you need to do any promotion or other disassembly (in a pipeline), then you need to recognize the message and there you think about xml etc.<BR/>Cheers,<BR/>BenjyAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-19890711.post-45295361154248086822008-10-16T01:29:00.000+10:002008-10-16T01:29:00.000+10:00Thanks for this post. I'm currently studying up on...Thanks for this post. <BR/><BR/>I'm currently studying up on BizTalk for a role involving finding out where and when it would help partner and customer businesses. One thing I need to learn is when they should use BizTalk, and when I should get them to talk to the SSIS team. This post was a good summary for me to start from.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-19890711.post-1859587183138549142008-04-03T04:00:00.000+10:002008-04-03T04:00:00.000+10:00Rick,Thanks for you feedback. The post has been up...Rick,<BR/><BR/>Thanks for you feedback. The post has been updated.Marcus Rosenhttps://www.blogger.com/profile/05678723267559173458noreply@blogger.comtag:blogger.com,1999:blog-19890711.post-77941045932628813872008-04-03T02:49:00.000+10:002008-04-03T02:49:00.000+10:00The description of Service Broker above is complet...The description of Service Broker above is completely inaccurate.<BR/>Service Broker. Service Broker is a FIFO queue but supports the concept of conversations (think TCP sessions). A conversation is a logical grouping of messages and gurantees exactly once in order. You can have many converstaions active on queue at one time and the conversations can be processed in parallel. Service Broker is an async, reliable network protocol so once you send the message the Service Broker infrastructure will try to send the message, if it can't make a connection it will keep trying until it is successful or the conversation is ended. Service Broker is highly scalable. We have customers moving on the order of 20,000 messages per second. It is used by customers in a variety of ways including real time data integration. It is true that Service Broker does not yet support a publish subscribe model. This is something we are looking at building.<BR/><BR/>Rick Negrin<BR/>SQL Server Program ManagerAnonymousnoreply@blogger.com