AS Processing Task

When using the AS processing task with a connection to "an Analysis Services project in this solution", only some processing options are available for processing dimensions. For instance, it is not possible to select "Process Update". Once I change the connection manager to point to the deployed cube database, I can choose from all the options. Is this by design?I have searched the documentation and the net for information on this. I have not been able to find an explanation. Anyone? At all?

Articles on foreach loop container over dataflow task?

Hi everyone,

do you know any articles on foreach loop container that loops over a dataflow task...pls tell me....

thanks in advance,

Praveen Dayanithi wrote:

Hi everyone,

do you know any articles on foreach loop container that loops over a dataflow task...pls tell me....

thanks in advance,

I presume that you mean a ForEach loop that contains a data flow.

Enumerating files in a Foreach loop
(http://blogs.conchango.com/jamiethomson/archive/2005/05/30/1489.aspx)

-Jamie

|||

Hi,

Thanks Jamie...

But i was looking for articles that involves foreach loop container that has a data flow task...

By saying dataflow task i mean i am goin to loop around all the records in the recordset of the dataflow task.

or you can tell me how to solve this issue....

I need to fetch data from table 2 for every record from the recordset which is mergejoin resultset of table1 and table2.

Thanks in advance,

ArrayList -> System.Object-Variable

Hi,

I have a custom task to execute a package. This task sets dynamically the values of the child package at runtime before execution of the child.

Everything works fine, as long as Im not trying to use an Object Variable in the child package, trying to fill with an ArrayList. Then, during package validation at runtime, the Properties of the custom task have NULL-Values. I don't know why all Properties got NULL or 0 (int), only adding an ArrayList-Property to the Task-Code.

The ArrayList gets initialized in the constructor of the Task. Values to add in execute(). But the process never gets to the execute()-Method, due to my check in validate() for null Values. So the List is initialized but empty.

Anyone an idea, maybe I'm doing something wrong at all. Anybody experiences with Object-Variables in Packages? A HowTo?

Thanks a lot

Thorsten

When you say you have an System.Object variable, are you referring to an SSIS variable of type Object, or a .NET variable/property of type System.Object?

Also, to get the picture correct. It sounds like this custom task is similar to an Execute Package Task, except that it sets the "values" of the child package at run-time. I assume you're familar with parent package configurations for non-object variables. Anyway, when you say "dynamically sets the values " are you referring literally to properties, as in pkg.SomeAttribute, or variables, as in pkg.Variables...?|||

Hi,

to get some light into the deep darkness I provided. Maybe, man should read over and over and over a post to provide all information :-). Sorry.

I refer to a SSIS Variable of Type Object. The task is similar to a execute package task, except of the UI, which provides a user friendly (non-technics :-)) GUI to set some properties of the task. These properties control the behavior of the package the task executes at runtime.

Yes I'm familiar with package configurations, but they need variables, one can change without the ability to know they link to a special task. Not so with properties, cos you have to explicitit mark the task to change them.

At runtime, I'm setting the variables of the package I wanna execute, by

Variables variables = null;
variableDispenser.LockOneForWrite(name, ref variables);
variables[0].Value = value;
variables.Unlock();

Everything works as expected, as long as I'm not trying to set a SSIS-Object Variable with an ArrayList. Then "NONE" of the vars gets setted.