I'm using Decision Support Objects (DSO) to build cubes. Two questions:

1) Once I've called myCube.Process(ProcessTypes.processFull) how do I get
status information they way analysis manager does? Being able to query for
number of rows processed so far would be immensely helpful in providing user
feedback.
2) If I set ServerClass svr.ConnectTimeout=2*60 will that automatically stop
all cube builds that take longer than 2 hours?

Hi,
for the first question see what Dave Wickert answer to my yesterday post.

for the second, ConnectTimeout is timeout value, in seconds so you have to
use 2 * 3600
but I don't think you obtain what you want because probably you'll only be
losing the connection after 2 hours.


--
Francesco De Chirico

E-Mail f.dechirico (AT) forgroup (DOT) it
"David Talbot" <DavidTalbot (AT) discussions (DOT) microsoft.com> ha scritto nel
messaggio news:93E61BD7-8506-44CB-A10E-3DAC717A68DB (AT) microsoft (DOT) com...

Ouch... so I'd have to attach to a log file and watch it grow to provide user
feedback... It is a solution none-the-less.

"Francesco De Chirico" wrote:

ah.. I didn't mean to say that. Sorry if you took it that way.

If you are programming via DSO, the second part of the post was a pointer to
the Parallel Processing Utility which is written in VB and is included with
source. You can look at the Partition Processing executable source to see
how you create an event and get callbacks with progress messages and other
information about the specific processing request your code is doing. This
is just like what Analysis Manager does. When you install the download, look
in the source folder.
http://www.microsoft.com/downloads/d...DisplayLang=en

The stuff I said about the log file was for *long-term* trend analysis, i.e.
did a 3-shift DBA inadverently do an incremental process on a changing
dimension at 2AM and that is why the system is 100% CPU pegged this morning
when you came in, or hey, I noticed that processing is now taking 8 hrs
rather than the 3 hrs I remembered -- if you look in the log, it contains
the SQL statement and you might notice that one of the dimensions became
unoptimized so additional joins have crept into the processing - - - that
kind of thing.

Hope that helps.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"David Talbot" <DavidTalbot (AT) discussions (DOT) microsoft.com> wrote