Processing Options and Settings (Analysis Services)

  • Article
  • 7 minutes to read

Applies to: SQL Server Analysis Services Azure Analysis Services Ability BI Premium

When you process objects in Microsoft SQL Server SQL Server Assay Services, yous can select a processing option to control the blazon of processing that occurs for each object. Processing types differ from one object to another, and by changes that have occurred to the object since it was last processed. If y'all enable SQL Server Assay Services to automatically select a processing method, it volition utilise the method that returns the object to a fully candy state in the to the lowest degree time.

Processing settings allow y'all control the objects that are processed, and the methods that are used to process those objects. Some processing settings are primarily used for batch processing jobs. For more information about batch processing, see Batch Processing (Analysis Services).

Processing Options

The post-obit table describes the processing methods that are available in SQL Server Assay Services, and identifies the objects for which each method is supported.

Mode Applies to Description
Process Default Cubes, databases, dimensions, measure groups, mining models, mining structures, and partitions. Detects the process state of database objects, and performs processing necessary to deliver unprocessed or partially processed objects to a fully processed land. If you change a data binding, Process Default will do a Process Full on the afflicted object.
Process Total Cubes, databases, dimensions, measure groups, mining models, mining structures, and partitions. Processes an SQL Server Analysis Services object and all the objects that it contains. When Procedure Full is executed against an object that has already been processed, SQL Server Analysis Services drops all data in the object, and then processes the object. This kind of processing is required when a structural alter has been made to an object, for instance, when an attribute hierarchy is added, deleted, or renamed.
Process Clear Cubes, databases, dimensions, measure groups, mining models, mining structures, and partitions. Drops the data in the object specified and any lower-level constituent objects. Afterwards the data is dropped, it is not reloaded.
Process Data Dimensions, cubes, measure groups, and partitions. Processes information just without building aggregations or indexes. If there is data is in the partitions, it will be dropped before re-populating the division with source data.
Process Add together Dimensions, measure out groups, and partitions

Note: Procedure Add is not available for dimension processing in Management Studio, but you can write XMLA script performs this activeness.

 For dimensions, adds new members and updates dimension attribute captions and descriptions.

For measure groups and partitions, adds newly available fact data and process only to the relevant partitions.
Procedure Update Dimensions Forces a re-read of information and an update of dimension attributes. Flexible aggregations and indexes on related partitions will be dropped.
Process Alphabetize Cubes, dimensions, measure groups, and partitions Creates or rebuilds indexes and aggregations for all processed partitions. For unprocessed objects, this option generates an error.

Processing with this option is needed if you turn off Lazy Processing.
Process Structure Cubes and mining structures If the cube is unprocessed, SQL Server Analysis Services will process, if it is necessary, all the cube's dimensions. After that, SQL Server Assay Services will create only cube definitions. If this option is applied to a mining structure, it populates the mining structure with source information. The difference betwixt this selection and the Process Total option is that this option does not iterate the processing down to the mining models themselves.
Procedure Clear Structure Mining structures Removes all grooming information from a mining structure.

Processing Settings

The following table describes the processing settings that are available for employ when y'all create a process operation.

Processing Option Description Option value
Parallel Used for batch processing. This setting causes SQL Server Assay Services to fork off processing tasks to run in parallel inside a single transaction. If in that location is a failure, the effect is a coil-back of all changes. Yous tin can ready the maximum number of parallel tasks explicitly, or let the server decide the optimal distribution. The Parallel selection is useful for speeding up processing.
Sequential (Transaction Mode) Controls the execution behavior of the processing chore. Two options are available.

When you process using 1 Transaction, all changes are committed subsequently the processing chore succeeds. This means that all SQL Server Analysis Services objects affected by a item processing job remain available for queries until the commit process. This makes the objects temporarily unavailable. Using Separate Transactions causes all objects that are afflicted by a process in processing chore to exist taken unavailable for queries as presently as that process succeeds.

 One Transaction. The processing job runs equally a transaction. If all processes inside the processing chore succeed, all changes by the processing job are committed. If one process fails, all changes by the processing job are rolled dorsum. 1 Transaction is the default value.

Separate Transactions. Each process in the processing chore runs every bit a stand-alone job. If ane procedure fails, just that process is rolled back and the processing job continues. Each task commits all process changes at the end of the task.
Writeback Table Option Controls how writeback tables are handled during processing. This option applies to writeback partitions in a cube. Use Existing. Uses the existing writeback tabular array. This is default value.

Create. Creates a new writeback table and causes the process to fail if one already exists.

Create Always. Creates a new writeback table fifty-fifty if ane already exists. An existing table is deleted and replaced.
Process Affected Objects Controls the object scope of the processing job. An afflicted object is defined past object dependency. For example, partitions are dependent on the dimensions that determine assemblage, but dimensions are not dependent on partitions. Faux is the default setting. False. The job processes the objects explicitly named in the job and all dependent objects. For example, if the processing job contains only dimensions, SQL Server Analysis Services processes simply those objects explicitly identified in the chore. If the processing task contains partitions, segmentation processing automatically invokes processing of afflicted dimensions.

True. The chore processes the objects explicitly named in the job, all dependent objects, and all objects affected by the objects existence processed without changing the land of the affected objects. For case, if the processing job contains only dimensions, SQL Server Analysis Services also processes all partitions affected past the dimension processing for partitions that are currently in a processed state. Affected partitions that are currently in an unprocessed state are non processed. However, because partitions are dependent on dimensions, if the processing chore contains only partitions, partition processing automatically invokes processing of afflicted dimensions, fifty-fifty when the dimension is currently in an unprocessed state.
Dimension Key Errors Determines the action taken by SQL Server Assay Services when errors occur during processing. When you select Use custom error configuration, you tin can select values for the following actions to control fault-treatment behavior.

When you select Use default fault configuration, SQL Server Assay Services uses the error configuration that is set for each object being processed. If an object is set to use default configuration settings, SQL Server Analysis Services uses the default settings that are listed for each option.
Key error action. If a primal value does not yet exist in a record, ane of these actions is selected to occur: Convert to unknown. The fundamental is interpreted equally an unknown member. This is the default setting.

Discard record. The record is discarded.
Processing error limit. Controls the number of errors processed by selecting 1 of these options: Ignore errors count. This volition enable processing to continue regardless of the number of errors.

Cease on error. With this option, you control 2 additional settings. Number of errors lets you limit processing to the occurrence of a specific number of errors. On error activeness lets you determine the activeness when Number of errors is reached. Yous tin can select Stop processing, which causes the processing task to fail and coil back any changes, or End logging, which enables processing to continue without logging errors. Stop on mistake is the default setting with Number of errors gear up to 0 and On error action set to End processing.
The following error conditions. You tin set the option value to control specific error-handling behavior.

When yous select Utilize default error configuration, Analysis Services uses the error configuration that is prepare for each object being candy. If an object is set to use default configuration settings, Analysis Services uses the default settings that are listed for each pick.

 Key not establish. Occurs when a fundamental value exists in a division just does not exist in the respective dimension. The default setting is Report and continue. Other settings are Ignore error and Report and stop.

Duplicate cardinal. Occurs when more than than i key value exists in a dimension. The default setting is Ignore error. Other settings are Study and continue and Study and stop.

Null primal converted to unknown. Occurs when a key value is nix and the Cardinal fault action is ready to Convert to unknown. The default setting is Ignore error. Other settings are Written report and proceed and Report and cease.

Null cardinal not allowed. Occurs when Key fault action is set to Discard record. The default setting is Report and go on. Other settings are Ignore mistake and Report and stop.

Meet Also

Processing a multidimensional model (Analysis Services)