All about SharePoint best practice... ask me how
Moving SharePoint Search Index Location [ Posted on: 10-April-2008 ]

Typically in most default SharePoint installs the physical index used by the Search crawler is saved under "C:\Program Files\Microsoft Office Servers\12.0\Data\Applications" there you will see a guid based folder and within that some other folders. You can change this location when you install SharePoint for the first time. It is in fact recommended that this location should be changed to a separate disk location such as "D:\SharePoint\Data\" This ensures that your server will not run out of C:\ drive space and will also give faster performance for your Search Queries. In a multi server deployment where a dedicated Index/Query server is used this should always be planned prior to installation. Mike Taghizadeh has this covered in his previous post "Estimate MOSS Disk space requirements"

Typically after a base install of MOSS you need to start the "Windows SharePoint Services Search Service" (spsearch) via Central Administration or via the command line using STSADM. This will provision your Search database.

To view what is being indexed by the "spsearch" service and the current location of the Index open a command prompt and type: "stsadm -o spsearch -action list"

Search

So if you wanted to change the default index location from being "C:\Program Files\Microsoft Office Servers\12.0\Data\Applications" to "C:\SharePointIndex\New\" you can do so by typing the following command. "stsadm -o spsearch -indexlocation C:\SharePointIndex\New" this will update the index location to a new location you specify.

Search3

Moving the Shared Service Provider Index Location

Also when you provision the Shared Services Provider (SSP) you have the option of setting the Office SharePoint Server Index location for the "osearch" service or the Office SharePoint Server Search Service. This index is used when you specify content sources such as file shares or other repositories.

To move this index location without resetting the index you must use the following "stsadm -o editssp" command. To view the available options "editssp" type "stsadm -help editssp". So for example if you wanted to change the location from the default to "C:\OSEARCHINDEX\" you can run the following command.

stsadm -o editssp -title [SSPNAME] -indexlocation C:\OSEARCHINDEX

Search2

This will move your entire index to a new location without resetting the whole index.

Posted by Chandima Kulathilake | 3 Comments | Bookmark with:        
Tags: Administration, Deployment, Planning, SharePoint 2007

Comments and Feedback
Tuesday, 15 Jul 2008 11:27 by Greg Lewis
Thank you Chandirma. I have understood this, but I have a question. I have a client that wants to move the actual services. They are adding a new computer and want to place both indexing and query services on the new computer as an application server. The Central Administration in MOSS 2007 will not allow us to remove both index and query services... we have to have at least one on the existing computer, but we want neither. How can this be accomplished?
Thursday, 17 Jul 2008 01:55 by Chandima
@Greg
You will need to first add your server to the existing server farm.
Then you can change the role assignments to host the Index/Query role on the new server.
It is easier to move the "Query" role than the indexing role.
Moving the roles will result in an Index reset and will require everyting to be crawled again.
Check out Joel's article on topologies for Search.
My Search deploymnet article series also have these explained.
Saturday, 4 Oct 2008 04:44 by Angkor Stormy

Your Name: (Required)
Website URL:
Your Email:
(Will not be displayed)
Feedback and Comments: (Required)
Are you a person? Please enter the charachters in the box below.


 
View the privacy policy.

 
Tags
 
Affiliations
Microsoft MVP (Microsoft Office SharePoint Server)

MCTS - WSS/MOSS Configuration

CKS - Team Member Add to Technorati Favorites

View Chandima Kulathilake's profile on LinkedIn



Kindly hosted by:
Kindly hosted by Intergen





Chandima Kulathilake's Facebook profile