Set-PowerPivotEngineServiceInstance cmdlet

Sets the properties of a SQL Server Analysis Services instance on an application server.

Syntax

Set-PowerPivotEngineServiceInstance [-Identity <PowerPivotEngineServiceInstancePipeBind>] [-Confirm <switch>] [-DataCollectionInterval <Ushort>] [-EnableProcessingMode <switch>] [-EnableQueryMode <switch>] [-LastAccessedTime <Ushort>] [-MaximumConnectionLimit <Ushort>] [-MaximumDiskcache <Ushort>] [-MaximumParallelRefreshJobs <Ushort>] [-WarnOnLowCPUMachine <Ushort>] [-WarnOnLowCPUOlapService <Ushort>] [-WarnOnLowDisk <Ushort>] [-WarnOnLowMemory <Ushort>] [<CommonParameters>]

Description

The Set-PowerPivotEngineServiceInstance cmdlet is used to set the properties of a SQL Server Analysis Services instance on an application server.

Parameters

-Identity <PowerPivotEngineServiceInstancePipeBind>

Specifies the service instance for which you are updating properties. The value must be a valid GUID that uniquely identifies the object in the farm.

-Confirm <switch>

Prompts you for confirmation before executing the command. This value is enabled by default. To bypass the confirmation response in a command, specify Confirm:$false on the command.

-DataCollectionInterval <Ushort>

Specifies the data collection period used for calculating the numbers used for triggering health rules. Although the system is monitored constantly, the thresholds used to trigger health rule warnings are calculated using data that was generated over a predefined interval. The default interval is 4 hours. The server retrieves system and usage data collected over the previous 4 hours to evaluate the number of user connections, disk space usage, and CPU and memory utilization rates

-EnableProcessingMode <switch>

Specifies whether the server accepts data refresh requests. The default is true. If you turn off data refresh processing, the server will only handle on demand queries. By default, both EnableQueryMode and EnableProcessingMode are turned on, allowing the server to handle requests for both on-demand queries and data refresh processing.

-EnableQueryMode <switch>

Specifies whether the server accepts on-demand query requests for PowerPivot data. The default is true. If you turn off query mode, the server will only handle data refresh jobs. By default, both EnableQueryMode and EnableProcessingMode are turned on, allowing the server to handle requests for both on-demand queries and data refresh processing.

-LastAccessedTime <Ushort>

Specifies last-used criteria for emptying the cache when disk space is at the maximum limit. All cached files that were last accessed at the hourly interval you define are immediately deleted from the file system. The default is 4 hours. If the maximum disk space limit is reached, all databases that have been inactive for 4 hours or longer are deleted from the file system. Databases that are inactive but still in memory are unloaded and then deleted from the file system.

-MaximumConnectionLimit <Ushort>

Specifies the upper limit of user connections, over which the server is considered to have too many. Exceeding this limit triggers a health rule indicating that the server is handling more connections than it is expected to support. The default is 100. Valid values are 1 to 500.

-MaximumDiskcache <Ushort>

Specifies the amount of disk space allocated for caching PowerPivot data. PowerPivot data is cached on first request, when the data is loaded into memory. Data remains on disk even after it no longer actively used, to service subsequent connection requests for that same data. It is eventually removed if no one requests the data for a period of days, as specified by the MemoryDatabaseHoldLimit parameter on the PowerPivot service application object.

-MaximumParallelRefreshJobs <Ushort>

Specifies the number of data refresh jobs that can run concurrently on the server. The default is 1 job per CPU. If the server has 2 processors, you can set this value to 2.

-WarnOnLowCPUMachine <Ushort>

Sets a CPU threshold at which a health rule is triggered, warning that the physical server is running low on CPU. This value is expressed as a percentage. The default is 90%. This health rule is triggered if the CPU resources on the machine remains at or above 90% over a 4 hour period (as specified through the DataCollectionInterval parameter).

-WarnOnLowCPUOlapService <Ushort>

Sets a CPU threshold at which a health rule is triggered, warning that the SQL Server Analysis Services instance has insufficient CPU. This value is expressed as a percentage. The default is 80%. This health rule is triggered if the CPU resources used by Analysis Services server process (msmdsrv.exe) remains at or above 80% over a 4 hour period (as specified through the DataCollectionInterval parameter).

-WarnOnLowDisk <Ushort>

Specifies a percentage of available disk space, below which the server is consider to have insufficient space for caching data. When available disk space falls below this value, a health rule is triggered indicating that disk space is low. The default is 5. Valid values are 1 through 99.

-WarnOnLowMemory <Ushort>

Specifies a percentage of available memory that should always be unused by the server. On a SharePoint application server, a SQL Server Analysis Services instance should always have a small amount of memory in reserve that is always unused. Because the server is memory-bound for the majority of its operations, the server runs best if it does not run all the way to the upper limit.

The default is 5%. If reserved memory falls below this amount, a health rule is triggered warning that the server is low on memory. The 5% of unused memory is calculated as a percentage of memory allocated to Analysis Services. For example, if you have 200 GB of total memory, and Analysis Services is allocated 80% of that (or 160 GB), then the 5% of unused memory is 5% of 160 GB (or 8 GB).

<CommonParameters>

This cmdlet supports the common parameters: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable,OutBuffer and OutVariable. For more information, see About_CommonParameters.

Inputs and Outputs

The input type is the type of the objects that you can pipe to the cmdlet. The return type is the type of the objects that the cmdlet returns.