Skip to main content

Change the location of the index file in MOSS 2007

Last week I noticed in our Production environment that the index server is running with low disk space. After that I tried to change the drive location of index.

The below are the steps to change the index location:

Prerequisites:

· Pause all content sources that are currently crawling content. After the index has been moved to the new location we have to resume the crawl that we have paused.

Change the location of the index file

Perform the following steps to change the index file location. Note that this procedure copies the index to the new location – it does not delete the content index in the original location. You can choose to delete the files in the original location later in this article.

1. Log on to the index server as a member of the Administrators group.

2. Open a command prompt.

3. Type the following and then press ENTER to go to the folder that contains the stsadm.exe command-line utility.

cd %COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\bin

4. Type the following and then press ENTER to move the content index to the new location.

stsadm –o editssp –title sspname -indexlocation drive:\folder

where sspname is the name of the shared services provider that is associated with the content index.

drive:\folder is the new location to which you want to move the content index.

For example : stsadm -o editssp -title Sharedservices1 -indexlocation e:\Data\MOSS_Search_Index

Important:

The –indexlocation property must refer to an NTFS partition on a hard drive or SAN that is attached to the index server.

5. After the command prompt displays "Operation completed successfully" proceed to the next step.

(Optional) Delete the content index from the original location.

You can choose to delete the content index from the original location. To do so, use Windows Explorer to delete the original file location.

Resume crawls and restore

If you paused crawls earlier, you can now resume those crawls.

Comments

Popular posts from this blog

How to get SPUser or SPGroup from Person or Group field

You have person or group field in SharePoint list and you want to programmatically get the user or person. The below code to gets SPUser from User or Group field in the list when multiple choice and Groups are not allowed in the field: //get SPUser SPFieldUser userField = (SPFieldUser)item.Fields.GetField("Users"); SPFieldUserValue userFieldValue = (SPFieldUserValue)userField.GetFieldValue(item["Users"].ToString()); SPUser user = userFieldValue.User; This part of code would help you to get SPUser when multiple choice is allowed and groups are not allowed: //Multiple choices are allowed SPFieldUser userField = (SPFieldUser)item.Fields.GetField("Users"); SPFieldUserValueCollection userFieldValueCollection = (SPFieldUserValueCollection)userField.GetFieldValue(item["Users"].ToString()); foreach (SPFieldUserValue userFieldValue in userFieldValueCollection) {     Console.WriteLine("     " + userFieldValue.User.LoginName); } And when group

SharePoint publishing page scheduling

In SharePoint 2010 publishing enabled team site collection is not showing schedule button in publish ribbon. Solution: Here is how to enable it  though the UI: Locate the SharePoint Server Web site on which you want to enable content approval and item scheduling. Click  Site Actions , click  Site Settings , and then click  Modify Pages Library Settings . Under  General Settings , click  Versioning Settings . Click  Yes  next to  Content Approval , and then click  OK . Click  Manage item scheduling .   Click to enable the  Enable scheduling of items in this list  check box, and then click  OK .

Changing Content Type Hub URL

Change the Hub URL through powershell by using: Set-SPMetadataServiceApplication -Identity " " -HubURI " " For Ex: Set-SPMetadataServiceApplication -Identity "Managed Metadata Service" -HubURI "http://contenttype.Domain.Com" When you try to do this you get this rather scary message: This is SharePoint telling you that this is a major thing so be careful! Essentially all your content types that you have published out will be removed if they can, and you have to republish all of your content types out again which can cause some issue.