.png)
Move-SPEnterpriseSearchLinksDatabases
Published: July 16, 2012
Applies to: SharePoint Server 2013 Enterprise | SharePoint Server 2013 Standard | SharePoint Foundation 2013
Moves data across links databases.
Move-SPEnterpriseSearchLinksDatabases [-SearchApplication] <SearchServiceApplicationPipeBind> [[-RepartitioningId] <Nullable>] [[-SourceStores] <LinksStore[]>] [[-TargetStores] <LinksStore[]>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]]
Parameters
| Parameter | Required | Type | Description | ||
|---|---|---|---|---|---|
| SearchApplication | Required | Microsoft.Office.Server.Search.Cmdlet.SearchServiceApplicationPipeBind | Specifies the search application that contains the links database. The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. | ||
| RepartitioningId | Optional | System.Nullable | Resumes the move with this identifier. | ||
| SourceStores | Optional | Microsoft.Office.Server.Search.Administration.LinksStore[] | Specifies a source list of databases. If this parameter is not specified then all currently existing links databases will be used as a source list. | ||
| TargetStores | Optional | Microsoft.Office.Server.Search.Administration.LinksStore[] | Specifies a target list of databases. If this parameter is not specified then all currently existing links databases will be used as a target list. | ||
| 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 | ||
| 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 | ||
| SearchApplication | Required | Microsoft.Office.Server.Search.Cmdlet.SearchServiceApplicationPipeBind | Specifies the search application that contains the links database. The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object. |
Note: Detailed Description
The Move-SPEnterpriseSearchLinksDatabases cmdlet moves data across a given list of links databases during farm configuration and scale out, to improve the performance and resource load of the farm. Once the move has started, the cmdlet will return a unique identifier, the RepartitioningId. Use this identifier to retrigger if the current run fails. After the move has finished, the old databases can be removed.
A links database stores query logging and analytics information.
Input Types
Return Types
--------EXAMPLE--------
$ssa=Get-SPEnterpriseSearchServiceapplication $ssa | New-SPEnterpriseSearchLinksDatabase -DatabaseName "links1" $ssa | New-SPEnterpriseSearchLinksDatabase -DatabaseName "links2" $ssa | New-SPEnterpriseSearchLinksDatabase -DatabaseName "links3" $dbs = $ssa | Get-SPEnterpriseSearchLinksDatabase $ssa | Repartition-SPEnterpriseSearchLinksDatabases -TargetStores $dbs
This example adds 3 new links databases and uses Move-SPEnterpriseSearchLinksDatabases to move data from the current links databases into new databases.
Change History
| Date | Description |
|---|---|
| July 16, 2012 | Initial publication |
