Change a process control setting for the data warehouse or Analysis Services cube

You can change the refresh frequency and time-out values that control the processing of the data warehouse. You change a process control setting only if you want to tune it for your specific deployment.

During processing, the warehouse adapters pull data from the operational store, transform it as necessary, and write it to the warehouse through the warehouse object model. During typical operations, the relational database (Tfs_Warehouse) is processed within two minutes of changes made to an operational store, and the SQL Server Analysis Services cube (Tfs_Analysis) is processed every two hours.

You might want to decrease or increase the length of time between refreshes to reduce the processing time or reduce the resource demands on the server. You can view the current settings or change a process control setting by using the Warehouse Control Web service.

You can determine the current settings and change a setting by using the Warehouse Control Web service.

Requirements

  • SQL Server Reporting Services must be configured for the TFS deployment. If it isn’t, see Add a report server.

  • You must be a member of the Team Foundation Administrators security group, or you must have the server-level Administer warehouse permission set to Allow. See Set administrator permissions for Team Foundation Server.

  • The Microsoft Team Foundation Server Application Pool must be running for the Warehouse Control Web service to be available.

  1. Log on to the application-tier server.

  2. Open a web browser, type the following string in the Address bar, and then press ENTER:

    http://localhost:8080/ VirtualDirectory /TeamFoundation/Administration/v3.0/WarehouseControlService.asmx

    For VirtualDirectory, type the IIS Virtual Directory that was specified when TFS was installed. By default, the virtual directory is tfs.

    The WarehouseControlWebService page opens.

You can change the refresh frequency of the data warehouse or other process control setting. For a list of all settings, go to Process control settings.

To change the refresh frequency of the data warehouse

  1. From the WarehouseControlWebService page, click ChangeSetting.

  2. In the settingID box, type:

    RunIntervalSeconds

  3. In the newValue box, type the new number in seconds, and then click Invoke.

    A confirmation Web page appears and indicates that the RunIntervalSeconds setting has been changed.

To change the refresh frequency of the cube

  1. From the WarehouseControlWebService page, click ChangeSetting.

  2. In the settingID box, type:

    IncrementalProcessIntervalSeconds

  3. In the newValue box, type the new number in seconds, and then click Invoke.

    Important note Important

    If you reduce the interval to less than the default of two hours (7200 seconds), processing of the data warehouse will consume server resources more frequently. Depending on the volume of data that your deployment has to process, you may want to reduce the interval to one hour (3600 seconds) or increase it to more than two hours.

    A confirmation Web page appears and indicates that the IncrementalProcessIntervalSeconds setting has been changed.

To change another process control setting

  1. From the WarehouseControlWebService page, click ChangeSetting.

  2. On the ChangeSetting page, type an entry for the settingID and newValue, and then click Invoke.

    For a description of each setting and the default values and measures that are assigned to each setting, see the table under Process control settings.

    A browser window will open. The service indicates that the setting has been changed to the new value.

All reportable data from all team projects that are defined in all team project collections for an on-premises TFS deployment is written to a single relational database (Tfs_Warehouse). Data from that warehouse is then processed and written to the SQL Server Analysis Services cube (Tfs_Analysis).

You should leave most of these settings at their default assignments. However, on occasion, you may have to modify a setting to meet your specific deployment requirements.

The following table describes each process control setting and provides the SettingID, default value, and unit of measure.

SettingID

Default value

Description

AnalysisSchemaUpdateWaitSeconds

3600 (seconds)

Specifies the time-out that determines how long a job will wait in a running state to perform an update to the cube. If the time-out expires before the schema change finishes, the job quits and restarts later. This time-out interval supports jobs that require exclusive access to the data warehouse resources during the schema change stage.

AnalysisServicesProcessingTimeout

86400 (seconds)

Specifies the time-out, measured in seconds, that determines how long a job will wait for a processing call to Analysis Services to finish.

DailyFullProcessingTime

02:00:00.0000000-08:00

Specifies the time of day when the full processing of the Analysis Services cube is started. By default, it is set to 2 AM.

DataUpdateWaitSeconds

30 (seconds)

Specifies the time-out that determines how long a job will wait in a running state for another adapter that is making schema changes to finish, or for the analysis processing job that changes the cube schema to finish. This time-out is used by jobs to acquire shared access to the warehouse resources during the data change stage. If the time-out expires before the schema change process finishes, the job quits and restarts later.

FullProcessIntervalSeconds

86400 (seconds)

Specifies the frequency at which the cube is fully processed. The default value corresponds to 24 hours.

IncrementalProcessIntervalSeconds

7200 (seconds)

Specifies the frequency at which the cube is incrementally updated. The default value corresponds to two hours.

MaxParallelASProcessingCommands

0

Indicates the maximum number of commands that can run in parallel when Team Foundation processes calls to SQL Server Analysis Services. If set to 0, the instance of SQL Server determines the optimal number based on the number of processors that are available on the computer.

RunIntervalSeconds

120 (seconds)

Specifies the frequency at which the relational database is updated.

SchemaUpdateWaitSeconds

120 (seconds)

Specifies the time-out that determines how long a job will wait in a running state to acquire exclusive access to the schema change method. If the time-out expires before the schema change finishes, the job quits and restarts later.

WarehouseCommandSqlTimeout

3600 (seconds)

Specifies the time-out that determines how long a job will wait to acquire an exclusive access to a data warehouse resource.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2015 Microsoft