ProcessTypes

[!참고]   이 기능은 다음 버전의 Microsoft SQL Server에서 제거됩니다. 새 개발 작업에서는 이 기능을 사용하지 말고, 현재 이 기능을 사용하는 응용 프로그램은 가능한 한 빨리 수정하십시오.

Enumerates values for the Option parameter of the Process method.

Constant	Description
processBuildStructure	Applies only to cubes. Processing a cube ordinarily causes the Analysis server to read all source data corresponding to the definition of the cube, create the cube, and populate it with data. This option causes the Analysis server to create the cube (that is, build its structure) but not populate it with data. Instead, the cube exists as an empty shell on the server. A user can connect to the cube, but it contains no data. This option can have performance benefits. If you do not use this option (see processDefault), the partitions in a cube are processed sequentially. If you do use it, you can process the partitions in parallel.
processDefault	The default option. It causes the system to decide what processing method is best. Typically this means that the system will try to refresh the object's data (processRefreshData) unless its structure has changed or it no longer exists. In the latter case, the system will perform a full processing (processFull).
processFull	Causes the object to be fully processed or rebuilt. The object's structure is changed if needed and its data is refreshed (that is, discarded and repopulated). This is the most complete type of processing supported. See processRefreshData.
processReaggregate	Applies only to cubes and partitions. This option is similar to processRefreshData, except that it instructs the Analysis server to rebuild maps, full indexes, and aggregations for multidimensional OLAP (MOLAP) partitions.
processRefreshData	Causes the object data to be refreshed (that is, discarded and repopulated), but does not change the object's structure. This operation occurs inside a transaction, allowing you to continue using current data while the transaction takes place. When the transaction is committed, the new data is available. See processFull.
ProcessRefreshDataAndIndex	Applies only to cubes and partitions. Similar to processRefreshData, except this option instructs the Analysis server to build full indexes for the partitions.
processResume	Directs the Analysis server to resume responding to user queries against a cube that has had queries suspended. The Analysis server will automatically resume responding to queries after 5 minutes unless processResume is received first.
processSuspend	Directs the Analysis server to suspend responses to user queries against a cube so your application can perform operations such as merging fact tables. The Analysis server automatically resumes responding to queries after 5 minutes (earlier if you submit a processResume request).

Suspend Timeout

The timeout value for the processResume and processSuspend constants can be changed by using the following registry key:

\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLAP Server\
Olap Manager Info\SuspendTimeout

The registry key stores the value as a long integer representing the timeout in milliseconds. For example, to change the timeout to 2 minutes, the value would be set to 120000. If the registry key is missing, the default value of 5 minutes (300000 milliseconds) is used by Decision Support Objects (DSO).

Processing and Dependent Objects

The DSO hierarchy can be complex, involving objects that depend on other objects. This is particularly true of mining model objects, which may have dependent virtual cube or mining dimension objects.

If the object to be processed depends on other objects, such as a mining dimension which, in turn, depends on an OLAP mining model, processing the object will cause the objects on which it depends to be processed, but only if the State property of the objects on which it depends is not set to olapStateCurrent.

If other objects depend on the object to be processed, such as an OLAP mining model with an associated mining dimension or a virtual cube, processing the object causes the dependent objects to be processed, but only if the State property of the dependent objects is not set to olapStateNeverProcessed.