Databases Reference
In-Depth Information
Logging processing errors is a costly operation. You should log errors only while design-
ing your application. After you have worked through all your issues and referential
integrity problems with relational data, you can configure your processing to stop logging
on key errors.
Processing Error Handling
While processing Analysis Services objects, you can receive any number of errors not
related to data. You encounter errors while connecting to a relational database, errors
finding tables or columns in a relational database, timeout errors waiting for a relational
database to respond, Analysis Services can run out of memory, and so on.
Every processing thread can encounter an error independent of others. It raises a flag and
informs other threads involved in the processing to cancel processing operations. Every
thread independently logs error conditions, too. After all threads terminate, the Job
Coordinator gathers all the errors and warnings from all the threads and generates the
response. The response of the
Process
command contains a collection of errors from all
processing threads. You should look closer at the returned result of the
Process
command,
and use the information it provides to investigate the cause of the processing failure.
NOTE
Sometimes a progress report might lose some trace events and important information
about errors. Therefore, we recommend that you analyze the return result of the
Process
command in the bottom of the Processing dialog.
You should analyze the return result of the
Process
command from the bottom up. The
last error usually is the one that caused the processing to fail. The rest of the errors usually
report from higher levels of execution.
Error handling is a costly operation. It could take some time for every processing thread to
notice the cancel flag raised by another thread. Some of the threads could be sleeping,
waiting for some resource to become available, and therefore not checking for any flag at
all. For example, a Read Data thread can go into the sleep state waiting for a SQL query
result.
Search WWH ::
Custom Search