Deployment Script Files - Specifying Processing Options
APPLIES TO: SQL Server Analysis Services Azure Analysis Services Power BI Premium
The Analysis Services Deployment Wizard reads the processing options from the <project name>.deploymentoptions file. Visual Studio with Analysis Services projects creates this file when you build the Microsoft SQL Server Analysis Services project. Visual Studio with Analysis Services projects uses the processing options specified on the Deployment page of <project name> Properties Pages dialog box to create the <project name>.deploymentoptions file.
Reviewing the Processing Options for Deployment
The configuration settings stored within the <project name>.deploymentoptions file are as follows:
Processing Method This setting controls whether the deployed objects are processed after deployment and the type of processing that will be performed. There are three processing options:
Default processing (default) detects the process state of database objects, and performs processing necessary to deliver unprocessed or partially processed objects to a fully processed state.
Full processing processes an object and all the objects that it contains. When Process Full is executed against an object that has already been processed, Analysis Services drops all data in the object, and then processes the object.
None means no processing is performed.
Writeback Table Options If writeback is enabled in the Analysis Services project, this setting defines how writeback is handled. There are three writeback table options:
By default, if a writeback table exists, it will be used. If a writeback table does not exist, a new writeback table will be created.
If a writeback table already exists, the deployment fails. If a writeback table does not exist, a new writeback table will be created.
Regardless of whether a writeback table already exists, a new writeback table will be created. In this case, the Analysis Services Deployment Wizard will delete any existing table and replace it with a new writeback table.
Transactional Deployment This setting controls whether the deployment of metadata changes and process commands occurs in a single transaction or in separate transactions.
If this option is True (default), Analysis Services deploys all metadata changes and all process commands within a single transaction.
If this option is False, Analysis Services deploys the metadata changes in a single transaction, and deploys each processing command in its own transaction.
Modifying the Processing Options for Deployment
However, you may need to deploy the Analysis Services project using different processing options than those stored in the <project name>.deploymentoptions file. For example, you may want to have all objects fully processed, or processed using the default processing option, or have no processing occur. If the cubes or dimensions are write-enabled, you can specify whether a new or existing writeback table be used.
To modify the processing options used during deployment, you can either edit and rebuild the project, or change the processing options in the input file by using one of the methods as described in the following procedure.
To change processing options after the input files have been generated
Run the Analysis Services Deployment Wizard interactively. On the Processing Options page, specify the processing options for the project being deployed.
Run the Analysis Services Deployment Wizard at the command prompt and set the wizard to run in answer file mode. For more information about answer file mode, see Running the Analysis Services Deployment Wizard.
Modify the <project name>.deploymentoptions file by using any text editor.