The Analysis Services Processing task processes Analysis Services objects such as tabular models, cubes, dimensions, and mining models.
When processing tabular models, keep the following in mind:
You cannot perform impact analysis on tabular models.
Some processing options for tabular mode are not exposed, such as Process Defrag and Process Recalc. You can perform these functions by using the Execute DDL task.
The options Process Index and Process Update are not appropriate for tabular models and should not be used.
Batch settings are ignored for tabular models.
Integration Services includes a number of tasks that perform business intelligence operations, such as running Data Definition Language (DDL) statements and data mining prediction queries. For more information about related business intelligence tasks, click one of the following topics:
Multiple objects can be processed at the same time. When processing multiple objects, you define settings that apply to the processing of all the objects in the batch.
Objects in a batch can be processed in sequence or in parallel. If the batch does not contain objects for which processing sequence is important, parallel processing can speed up processing. If objects in the batch are processed in parallel, you can configure the task to let it determine how many objects to process in parallel, or you can manually specify the number of objects to process at the same time. If objects are processed sequentially, you can set a transaction attribute on the batch either by enlisting all objects in one transaction or by using a separate transaction for each object in the batch.
When you process analytic objects, you might also want to process the objects that depend on them. The Analysis Services Processing task includes an option to process any dependent objects in addition to the selected objects.
Typically, you process dimension tables before processing fact tables. You may encounter errors if you try to process fact tables before processing the dimension tables.
This task also lets you configure the handling of errors in dimension keys. For example, the task can ignore errors or stop after a specified number of errors occur. The task can use the default error configuration, or you can construct a custom error configuration. In the custom error configuration, you specify how the task handles errors and the error conditions. For example, you can specify that the task should stop running when the fourth error occurs, or specify how the task should handle Null key values. The custom error configuration can also include the path of an error log.
The Analysis Services Processing task can process only analytic objects created by using the SQL Server tools.
This task is frequently used in combination with a Bulk Insert task that loads data into a SQL Server table, or a Data Flow task that implements a data flow that loads data into a table. For example, the Data Flow task might have a data flow that extracts data from an online transactional database (OLTP) database and loads it into a fact table in a data warehouse, after which the Analysis Services Processing task is called to process the cube built on the data warehouse.
The Analysis Services Processing task uses an Analysis Services connection manager to connect to an instance of Microsoft SQL Server Analysis Services. For more information, see Analysis Services Connection Manager.
Configuration of the Analysis Services Processing Task
You can set properties through SSIS Designer or programmatically.
For more information about the properties that you can set in SSIS Designer, click one of the following topics:
For more information about setting these properties in SSIS Designer, click the following topic:
Programmatic Configuration of the Analysis Services Processing Task
For more information about programmatically setting these properties, click one of the following topics: