|
Home > Archive > MS SQL Server OLAP > August 2005 > Best way to do writeback from .NET
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Best way to do writeback from .NET
|
|
| Adam Bieganski 2005-08-27, 11:23 am |
| Hi,
In our company we are developing and application which uses ADOMD.NET and
XMLA to connect Analysis Services and get data from it. ADOMD.NET is uses by
the business layer implemented as XML Web Services.
We've also included writeback functionality in our application, but we keep
having huge problems with its performance.
At first we were using UPDATE CUBE, but this was completely inefficient in
case of updating a larger number of values.
Then we decided to write values directly into the writeback table, first
reading all required metadata (e.g. writeback table's name, columns, etc.)
using DSO and ADOMD (not .NET) - which also forced us to use a special way
of instantiating COM objects in Web Services (since they're MTA).
But our writeback's performance is still unacceptable - writing back about
80 values takes more than 40 seconds!
I have a question then:
What IS the best way to do a multiple (more than, say, 20 values) writeback
from a .NET based application?
Thanks in advance for any answers.
Regards,
Adam Bieganski
Codec Systems Poland
| |
|
| its difficult to help you without your code.
I think the problem is not at the cube level.
do you use 1 transaction or multiple transactions?
do you update leaf levels of your cube or higher levels?
"Adam Bieganski" <adamb@codec.pl> wrote in message
news:OBS2ewxqFHA.3424@TK2MSFTNGP14.phx.gbl...
> Hi,
>
> In our company we are developing and application which uses ADOMD.NET and
> XMLA to connect Analysis Services and get data from it. ADOMD.NET is uses
> by the business layer implemented as XML Web Services.
>
> We've also included writeback functionality in our application, but we
> keep having huge problems with its performance.
> At first we were using UPDATE CUBE, but this was completely inefficient in
> case of updating a larger number of values.
> Then we decided to write values directly into the writeback table, first
> reading all required metadata (e.g. writeback table's name, columns, etc.)
> using DSO and ADOMD (not .NET) - which also forced us to use a special way
> of instantiating COM objects in Web Services (since they're MTA).
>
> But our writeback's performance is still unacceptable - writing back about
> 80 values takes more than 40 seconds!
>
> I have a question then:
> What IS the best way to do a multiple (more than, say, 20 values)
> writeback from a .NET based application?
>
> Thanks in advance for any answers.
>
> Regards,
> Adam Bieganski
> Codec Systems Poland
>
|
|
|
|
|