I have noticed a few fellow SQL bloggers over on SQLBlog.com (most notably Aaron Bertrand) have started to use their blog to draw attention to various submissions to Microsoft Connect that they believe to be worthy of attention. I think this a great idea, the more attention that are paid to Connect items the better hence I’m going to start calling out some SSIS related Connect submissions that I think are worthy of your attention.
Take a read of the items below and if you agree with the aim of the submission, please click through and vote for it – it only takes a few seconds. If you want to leave a comment supporting your vote, that would be even better.
Don’t feel obliged to vote on everything carte blanche, only vote for those that you would like the SSIS product team to concentrate on. Most of these are already closed but that doesn’t mean they can’t be opened again. And remember, voting really does make a difference; if you don’t believe me take a read of Doug Laudenschlager’s blog post Your vote on Microsoft Connect influenced SQL Server 2008 Service Pack 1.
Ability to view the contents of a raw file in the raw file source adapter
There is currently no way to view the contents of a raw file without running a package or using a 3rd party tool. This request is to allow us to view the contents of a raw file from within a raw source file adapter.
#124839: Let us view the contents of a raw file in the raw file source adapter
(https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=124839)
Execute from this point forward
The “Execute Task" option in BIDS is incredibly useful but is only executes one task at a time (aside: it wouldn’t have even done that had a certain someone not asked for it during the SQL Server 2005 beta period). It would be very handy to begin package execution from a particular task so that it executes that task and all subsequent tasks.
This would be a great time saver in situations where the first step in a package is to fetch lots of data from a source and stage it somewhere for processing. Quite often we may already have the data available in the staging area thus we only want to execute the subsequent processing steps.
#126372: Execute from here in control-flow
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=126372
Drop a component into an existing data path
If we need to add a new component into an existing data-flow we need to detach data paths and re-attach them all again.
It would be better if we could drag the new component on top of a data path and it automatically gets inserted in between the 2 components that the data path is connecting. Depending on the behaviour of the component (synchronous or asynchronous) this may create 2 new data paths with the new component in between.
#126475: Drag component into a data path
(https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=126475)
View a variable in OLE DB Source component
If, in an OLE DB Source component, DataAccessMode="SQL Command from variable" you have no idea what SQL statement is being issued without coming out of the editor and looking at the variable.
The component editor should display the contents of the variable in the OLE DB Source Editor.
#127221: View the contents of a variable in OLE DB Source component
(https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127221)
UPDATE: John Welch informed me that this one was actually fixed in SSIS2008 – which I have just confirmed to be true:
Let me know if you want me to carry on calling these out. I have many many more of them.
-Jamie