Home Dashboard Directory Help
Search

SSAS DDL Task in SSIS does not support Shared Connection Managers by Todd C


Status: 

Active


1
0
Sign in
to vote
Type: Suggestion
ID: 801623
Opened: 9/19/2013 9:53:10 AM
Access Restriction: Public
0
Workaround(s)
view

Description

Using either SSIS in SQL 2012 or 2008 R2, create an SSIS Package. Add an Analysis Server DDL Task to the Control Flow. Go through the steps to create a NEW Connection manager for this task.

now try to create a Shared Connection Manager at the Project level to be used by this task. Can't be done. Why not? Why can't I create a Project level Connection Manager that is THE SAME AS one that resides at the individual Package level.

For all their spouting of collection all the Connection Managers at the Project level to facilitate easy Configuration after Deployment, this kind of goes against the grain.

As it is, if I have 10 packages that all use the same SSAS Connection Manager for AS DDL tasks, I need to A) Copy and Paste the Cm into each package, and B) Configure EACH package after deployment.
Details
Sign in to post a comment.
Posted by Microsoft on 4/8/2014 at 8:58 PM
Hello
Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SSIS. The reasons for closing these bugs are following:
1.     The fix is risky to implement in the current version of the product
2.     Scenarios reported in the bug are not common enough
3.     A viable workaround is available.

If the issue is a critical business interruption, please call CSS (Customer Support Services).

Thanks again for reporting the product issue and continued support in improving our product.

Mariusz Cichomski
Program Manager
Microsoft
Posted by Microsoft on 4/8/2014 at 8:58 PM
Hello
Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SSIS. The reasons for closing these bugs are following:
1.     The fix is risky to implement in the current version of the product
2.     Scenarios reported in the bug are not common enough
3.     A viable workaround is available.

If the issue is a critical business interruption, please call CSS (Customer Support Services).

Thanks again for reporting the product issue and continued support in improving our product.

Mariusz Cichomski
Program Manager
Microsoft
Posted by Microsoft on 10/4/2013 at 12:25 PM
Hello, Todd.
Thanks for the feedback. We'll keep this item active so that other members of the community get a chance to see it an provide their own input. We'll keep an eye on it as we plan the next big things for SQL.
-Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)
Sign in to post a workaround.