Jamie Thomson : Connect, denalihttp://sqlblog.com/blogs/jamie_thomson/archive/tags/Connect/denali/default.aspxTags: Connect, denalienCommunityServer 2.1 SP2 (Build: 61129.1)Newly closed Connect items auger well for SSIS in Denalihttp://sqlblog.com/blogs/jamie_thomson/archive/2010/09/10/newly-closed-connect-items-auger-well-for-ssis-in-denali.aspxFri, 10 Sep 2010 11:56:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:28671jamiet1http://sqlblog.com/blogs/jamie_thomson/comments/28671.aspxhttp://sqlblog.com/blogs/jamie_thomson/commentrss.aspx?PostID=28671http://sqlblog.com/blogs/jamie_thomson/rsscomments.aspx?PostID=28671<P>Todd Mcdermid spoke recently on his blog post <A class="" href="http://toddmcdermid.blogspot.com/2010/08/integration-services-vnext-coming-soon.html" target=_blank>Integration Services vNext Coming Soon</A> about how some recently closed Connect items had encouraged him as to the future of SSIS. Also, Matt Masson from the SSIS team has written a similarly encouraging blog post about some upcoming SSIS enhancements at <A class="" href="http://blogs.msdn.com/b/mattm/archive/2010/08/25/upcoming-product-changes.aspx" target=_blank>Upcoming Product Changes</A>.</P>
<P>Now its my turn. Just this morning I had three Connect items returned to me as "fixed" and, like Todd, I'm&nbsp;delighted to see these items getting closed as such. I have long complained about the shortcomings of SSIS's logging framework as I don't believe it produces enough "context" as to why a container happens to be executing; the consequence being that we end up getting lost in a&nbsp;plethora of log records where we can't see how each one relates to another. These three Connect items give me hope that this issue is getting addressed in the next version of SSIS (aka SQL11 aka Denali).</P>
<P>The three Connect items in question are:</P>
<UL>
<LI><A class="" href="https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=126479" target=_blank>Can't differrentiate between multiple instances of a task running in parallel</A> - If a&nbsp;container happens to be running in parallel with another instance of itself (e.g. a dataflow task in a package that has been called from two Execute Package Tasks) there is no way to differentiate between the two. A solution would be to provide an Execution identifier for the execution of each container just like the ExecutionGUID that we get for a package.</LI>
<LI><A class="" href="https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=355956" target=_blank>Please put ExecutionGUID property on DtsContainer </A>- Pretty much the same as the last one</LI>
<LI><A class="" href="https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=207395" target=_blank>SSIS: Make container stack available</A> - This refers to what I call the <EM>context</EM> of a task being executed. We know that a task is executing but what are all the ancestral tasks and containers in the <A class="" href="http://consultingblogs.emc.com/jamiethomson/archive/2005/07/13/1792.aspx" target=_blank>container&nbsp;hierarchy</A> that have led to that task being executed?</LI></UL>
<P>The provision of more execution metadata for logging purposes&nbsp;gives me hope&nbsp;that the next version of SSIS will have a much better story around logging. Hopefully we won't have to wait long to find out.</P>
<P><A class="" href="http://twitter.com/jamiet" target=_blank>@Jamiet</A></P>
<P>&nbsp;</P><img src="http://sqlblog.com/aggbug.aspx?PostID=28671" width="1" height="1">sql serverConnectsql server integration servicesssisdenaliSQL Server 2012