Showing posts with label destination. Show all posts
Showing posts with label destination. Show all posts

Friday, March 23, 2012

ProcessRowInput not containing any Row data

I have a script component as a destination. I believe I'm doing something very simple, but for some reason, I'm not getting back any data.

When I just msgbox the data in Row.Address, I get nothing. If I msgbox Row.Address.toString, I get "Object reference not set to instance of an object."

Public Overrides Sub Input0_ProcessInputRow(ByVal Row As Input0Buffer)
MessageBox.Show(Row.Address)
End Sub

I have Address as an input and output column in my script component setup. Any help? It seems like it's gotta be something simple, but I'm pulling my (little bit of) hair out to find it.

mmmm... think my problem is elsewhere. thanks anyways!

Saturday, February 25, 2012

process add and configuration

SSIS Destination Adapter ProcessADD does not correctly use the Analysis Services Connection with and dynamic connection string.

I use process add for cube Processing - we use Production and Development environment. The analysis Services Connection is parameterized with a differnt Database name.

The Process add - does not like all other analysis services processing tasks, allow you to use an expression for the processing command - it only gives you the UI with design time tools.

But I guess like all other SSIS Components with SSAS the Database Name is hardcoded in the prcessing command. For the Processing Task I could change this with an expression.

But Howto change the Processing Command withing the Process ADD Destination -

or how do I get it working while the database name changes (at the moment if the database name changes by configuration all mappings are lost and execution fails)

Best Regards

HANNES

I am doing something wrong? or is a configuration for data datasource of the olap destination is ssis not supported?

Best regards, HANNES

|||

I got it

The Database is always part of the XMLA command and therefore not affected by the connection manager initial catalog property.

You always have to code the database name in the XML Command

HANNES

process add and configuration

SSIS Destination Adapter ProcessADD does not correctly use the Analysis Services Connection with and dynamic connection string.

I use process add for cube Processing - we use Production and Development environment. The analysis Services Connection is parameterized with a differnt Database name.

The Process add - does not like all other analysis services processing tasks, allow you to use an expression for the processing command - it only gives you the UI with design time tools.

But I guess like all other SSIS Components with SSAS the Database Name is hardcoded in the prcessing command. For the Processing Task I could change this with an expression.

But Howto change the Processing Command withing the Process ADD Destination -

or how do I get it working while the database name changes (at the moment if the database name changes by configuration all mappings are lost and execution fails)

Best Regards

HANNES

I am doing something wrong? or is a configuration for data datasource of the olap destination is ssis not supported?

Best regards, HANNES

|||

I got it

The Database is always part of the XMLA command and therefore not affected by the connection manager initial catalog property.

You always have to code the database name in the XML Command

HANNES