| external help file | Microsoft.SharePoint.PowerShell.dll-help.xml |
|---|---|
| Module Name | Microsoft.SharePoint.Powershell |
| online version | https://learn.microsoft.com/powershell/module/microsoft.sharepoint.powershell/reset-spsites |
| applicable | SharePoint Server 2016, SharePoint Server 2019 |
| title | Reset-SPSites |
| schema | 2.0.0 |
| author | techwriter40 |
| ms.author | pamgreen |
| ms.reviewer |
Synchronizes the content database with the configuration database of the farm.
Reset-SPSites [-Identity] <SPContentDatabasePipeBind> [-AssignmentCollection <SPAssignmentCollection>]
[-Confirm] [-WhatIf] [<CommonParameters>]
The Reset-SPSites cmdlet synchronizes the content database with the configuration database of the farm with respect to what site collections actually exist in the content database.
It also ensures that all site collections in the content database are registered in the configuration database and removes any site collection references in the configuration database if the site collection does not exist in the content database.
For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at Windows PowerShell for SharePoint Server 2016, SharePoint Server 2019 reference.
$contentdb = Get-SPContentDatabase ContentDbName
Reset-SPSites -Identity $contentDb
Synchronizes the sites in the content database named ContentDbName with the configuration database.
Applicable: SharePoint Server 2016, SharePoint Server 2019
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.
When the Global parameter is used, all objects are contained in the global store.
If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur.
Type: SPAssignmentCollection
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: True (ByValue)
Accept wildcard characters: FalseApplicable: SharePoint Server 2016, SharePoint Server 2019
Prompts you for confirmation before running the cmdlet.
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: FalseApplicable: SharePoint Server 2016, SharePoint Server 2019
Specifies a specific content database. This could either be ID or Name of the content database or a valid instance of a content database.
Type: SPContentDatabasePipeBind
Parameter Sets: (All)
Aliases:
Required: True
Position: 0
Default value: None
Accept pipeline input: True (ByValue)
Accept wildcard characters: FalseApplicable: SharePoint Server 2016, SharePoint Server 2019
Shows what would happen if the cmdlet runs. The cmdlet is not run.
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: FalseThis cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters (https://go.microsoft.com/fwlink/?LinkID=113216).
Microsoft.SharePoint.PowerShell.SPAssignmentCollection