AMO and ProcessAdd for dimensions

Is there any way to process a dimension using ProcessAdd using AMO without using xmla? We currently have an app for SQL2000 that processes dimensions using DSO - ProcessUpdate that a colleague insists can just be changed to AMO - ProcessAdd but I am not getting the impression that it is as simple as that.

A quick yes or no would be great!

Thanks

Hi,

You can do it, but this only add the new records to your dimension.

If your dimension data has updated records they will not be updated in SSAS dimension.

You can check this link

http://msdn2.microsoft.com/en-us/library/ms345142.aspx

Regards,

Raul

|||

Thanks for the response. However, I have read that link previously and the examples all show that xmla must be used. I was wondering something similar to this post:

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2147144&SiteID=17

rprs wrote:

Hi,

You can do it, but this only add the new records to your dimension.

If your dimension data has updated records they will not be updated in SSAS dimension.

You can check this link

http://msdn2.microsoft.com/en-us/library/ms345142.aspx

Regards,

Raul

AMO <-> XMLA serialization?

I'm in the process of developing additional tooling to help auto-partition my cube, and I've developed some AMO code to connect to my AS database to do this.

What I'm worried about is the fact that there's no good way to keep my online instance in sync with the persisted source code. IE, if I make a change in dev mode and re-deploy, all my auto-created partitions will be destroyed.

What's the best way to deal w/ this? I suppose I could constantly re-generate a BIDS project from the server every time I wanted to make a change. Or, if there was some way to deserialize the BIDS project files (since they're all XMLA anyway), I could apply my AMO code to the updated the XMLA object definitions.

Have you looked at the Deployment Wizard. I am pretty sure it has the option of deploying a solution without overwritting the existing partitions.