Posting XMLA to AS from java without msmdpump.dll

I'm simply trying to invoke an Analysis Server CLR assembly procedure using MDX from a non windows machine in a a java environment. I also wish to require as little configuration on the SQL Server machine as possible.

Posting the request via HttpURLConnection as below works.

url = new URL("http://localhost//olap//msmdpump.dll ");
HttpURLConnection con = (HttpURLConnection) url.openConnection();

The question is I'd prefer not to have to require IIS plus the pump to be running on the AS server(msmdpump.dll). We know MS code is sending XMLA to the AS Database.

Why can we not use the same channel? It may not be http but I do not care. I'd rather have minimum stuff to do on the server.

Thanks in advance

Zub

I'd say in this stiuation you are probably better off using HTTP. On windows machine you can use naitive AS client : ADOMD.NET or AS OLEDB, and establish connection using TCP/IP , but coming from outside you will face quite a few problems. Configuring virtual direcory compared to ... for instance trying to figure out how to authenticate your non-windows user if by far easier task.

Hope that helps.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Post processing data flow destinations

What I am trying to do is move data from a staging table into a live environment and then update the staging table AFTER the row has move (and not errored). There does not seem to be a reliable method for doing this.

Any assistance would be appreciated.

Brett Robson wrote:

What I am trying to do is move data from a staging table into a live environment and then update the staging table AFTER the row has move (and not errored). There does not seem to be a reliable method for doing this.

Any assistance would be appreciated.

What specifically isn't reliable? It sounds to me like you need a data-flow to move the data and an Execute SQL Task to issue the UPDATE. That should work OK.

-Jamie

|||

Jamie,

I don't think your quite following what I am trying to do. I want to update the SOURCE table after the rows have moved. I don't want to update the ones which error. How does the Execute SQL Task get the appropriate row ids? They certainly won't be passed from the data-flow.

Regards,

BRETT ROBSON

|||

Brett Robson wrote:

Jamie,

I don't think your quite following what I am trying to do. I want to update the SOURCE table after the rows have moved. I don't want to update the ones which error. How does the Execute SQL Task get the appropriate row ids? They certainly won't be passed from the data-flow.

Regards,

BRETT ROBSON

Oh OK. I gotcha.

You're right, Execute SQL Task is not an option. You can execute your UPDATE from the data-flow though using an OLE DB Command component.

This will work fine - the only problem with it is that it issues an UPDATE for every row - and ths isn't very performant. Another option is to push all the successful rows into another table and update the source table from this new table. This update can be issued from the Execute SQL Task and will be much more performant because you're only doing it once.

-Jamie

|||

Thanks Jamie - either of those two should work.

Possible to deploy website applications using MDF database file?

Hi,

A quick question, is it possible to deploy a website on a shared hosting environment which attaches to a MDF database file stored in the App_Data folder?

Hi,

you have to ask your hosting company for that. I once tested a host that supported it but I had to attach it on the host by using a dedicated screen.

Grz, Kris.