Set-SPUsageApplication
Published: July 16, 2012
Applies to: SharePoint Server 2013 Standard
Sets properties of a usage application.
Set-SPUsageApplication [-Identity] <SPUsageApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-DatabaseName <String>] [-DatabasePassword <SecureString>] [-DatabaseServer <String>] [-DatabaseUsername <String>] [-EnableLogging <SwitchParameter>] [-FailoverDatabaseServer <String>] [-UsageService <SPUsageServicePipeBind>] [-WhatIf [<SwitchParameter>]]
Parameters
| Parameter | Required | Type | Description | ||
|---|---|---|---|---|---|
| Identity | Required | Microsoft.SharePoint.PowerShell.SPUsageApplicationPipeBind | Specifies the usage application to update. The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh, a valid name of a usage application (for example; UsageApp1); or an instance of a valid SPServiceApplication object. | ||
| AssignmentCollection | Optional | Microsoft.SharePoint.PowerShell.SPAssignmentCollection | Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.
| ||
| Confirm | Optional | System.Management.Automation.SwitchParameter | Prompts you for confirmation before executing the command. For more information, type the following command: get-help about_commonparameters | ||
| DatabaseName | Optional | System.String | Specifies the name of the logging database. The type must be a valid name of a SQL Server database; for example, UsageLogDB1. If the logging database does not exist, a logging database will be automatically created. | ||
| DatabasePassword | Optional | System.Security.SecureString | Specifies the password for the user specified in DatabaseUserName. Use this parameter only if SQL Server Authentication is used to access the logging database. The type must be a valid password. | ||
| DatabaseServer | Optional | System.String | Specifies the name of the host server for the database specified in DatabaseName. The type must be a valid SQL Server host name; for example, SQLServerHost1. | ||
| DatabaseUsername | Optional | System.String | Specifies the user name to use for connecting to the logging database. Use this parameter only if SQL Server Authentication is used to access the logging database. The type must be a valid user name; for example, UserName1. | ||
| EnableLogging | Optional | System.Management.Automation.SwitchParameter | Specifies that this usage application collects usage data. | ||
| FailoverDatabaseServer | Optional | System.String | |||
| UsageService | Optional | Microsoft.SharePoint.PowerShell.SPUsageServicePipeBind | Specifies the SPUsageService object that is the parent of the usage application. The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a usage service (for example, UsageService1); or an instance of a valid SPUsageService object. | ||
| WhatIf | Optional | System.Management.Automation.SwitchParameter | Displays a message that describes the effect of the command instead of executing the command. For more information, type the following command: get-help about_commonparameters |
Detailed Description
The Set-SPUsageApplication cmdlet sets properties of a usage application.
Input Types
Return Types
-------------------EXAMPLE----------------------
Set-SPUsageApplication –Identity “Usage and Health data collection” –DatabaseServer “Server Name” -DatabaseName “New Logging DB”
This example changes the database server and database name used by the usage logging service to store logging data.
Change History
| Date | Description |
|---|---|
| July 16, 2012 | Initial publication |

Note: