I have the following script to process partitions..

dsoPartition.Process 1

Some time the process cannot be done because of error. How should I check if
the process has been done properly?

If you haven't already done so, you should ALWAYS setup the system-wide
processing log file. It is a best practice. Bring up Analysis Manager,
right-click on the server and select "Properties..." -- then go to the
Logging tab. Check that you want the system-wide processing log file and
enter a known good value, e.g. C:\OLAP_Processing.txt

Everything that you see interactively whenever you do processing will also
be written to that file, i.e. what object is processed, its SQL statement,
timestamps for start and finish, and an errors that were encountered are
written to the log -- along with the username who requested it.

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.

"nick" <nick (AT) discussions (DOT) microsoft.com> wrote

Thanks, however, I found the log of the processing done by a script cannot be
written in the file...

"Dave Wickert [MSFT]" wrote:

If you're reprocessing in full each time you run your script, I'd imagine
you're reprocessing all your dimensions first. In this case, the
LastProcessed property of a partition won't be accessible.

If you loop through your partitions in code after the processing is done,
you could check this with something like the following in your loop:

Set dsoPartition = dsoCube.MDStores(strPartition)
varProcessedDate = dsoPartition.LastProcessed

Have your error handler echo back, or do whatever you want, with the name of
the partition (be sure to do a resume next), since the second line will fail.


If you're reprocessing a partition that has already been processed (without
the dims having been reprocessed), you can use the above code to see if the
LastProcessed date/time was greater than the time you started your script.
If it is, it succeeded.


Good luck.


"nick" wrote:

Thanks, in fact I used this method to check it. Are there any way to validate
the structure is good? I found the script can change a lot of properties and
sometime it can assign a bad value (for example, an wrong string for fact
table, data source, dimension attributes, etc) and it's not easy to find it
out....

"SQL McOLAP" wrote: