Change Default Index File Location

Change Default Index File Location

In a farm environment it will be usually a requirement to have the index file location on a separate drive and folder as opposed to the default location which is:

"C:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications"

You can set this path for an SSP by using the UI through Central Administration. But to set the default path for Office SharePoint Server Search Service and for WSS Search Service you will have to set the location through STSADM command.


Office SharePoint Server Search Service is configured using OSEARCH command:

stsadm -o osearch -defaultindexlocation e:\Data\MOSS_Search_Index


(By default, the search index will be located at this path on this server. For index servers, you can specify a different path when you create an SSP.

Note:

Changing the index location will reset the index. To move an index with a reset, use the noreset parameter of the Spsearchsensitive or Osearchsensitive operation)

Windows SharePoint Services Search Service is configured using SPSEARCH command:

stsadm -o spsearch -indexlocation e:\Data\MOSS_Search_Index

(Configures the search server that has the location of where the index resides)

You can also set this path for already created SSP using EDITSSP command:

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

(Configures the search server that has the location of where the index resides. This parameter is used in conjunction with the osearch operation. )

Comments

  1. Firoz KhanMarch 14, 2015 at 10:36 AM

    Cursos Para Exce

    Provee explicaciones comprensivas y muy a fondo de Tablas Dinámicas. Los temas que se cubren empiezan siendo de nivel principiante hasta llegar a avanzado.

    ReplyDelete

Post a Comment

Popular posts from this blog

Using External Content Types with Stored Procedures with Input Parameters

Image
You must have tried External Content Types - the exciting new feature in SharePoint 2010 to connect to an external SQL table and provide a list where it lists, creates, updates data straight into the SQL table. People always wonder, how do you get a ECT to work with a Stored Procedure, one that has input parameters. You could do it this way... Step 1: In your SharePoint Designer 2010, create a new external content type Step 2: Connect to your SQL Server and then make sure you see the Routines (your stored procedures must be listed here) Step 3: Rt Click on the Stored Procedure name and create operations for "Read Item" and "Read List" - both are required for the External Content Type's SharePoint list to be created. During both these wizards, in the Input Parameters, your SP's Input Parameter will be listed. Here, you need to create a filter, which sends out it's value to the SP's filter. For example, if your SP's Input Parameter is @Emp...
Read more

Validate a SharePoint Date Field against Current Date in Javascript

Consider the following scenario: You have a SharePoint Site which has its regional settings set to English (UK) - so that the date format becomes dd/mm/yyyy in all date pickers You would like to validate a particular date field in your List or Document Library against the current date If the validation does not pass, you should not allow the form to save So what the script does is: Uses the sputility (check my previous posts and also look at http://sputility.codeplex.com) to get the particular SharePoint date field It comes out as a date datatype, so I cast it to string Since the format is in dd/mm/yyyy and Javascript compare and date functions work only with mm/dd/yyyy, I am converting them back to that format then using UTC string conversions and comparing... Enjoy! <script type="text/javascript"> function PreSaveAction() {  var createdate = SPUtility.GetSPField('Date of Creation').GetValue();  var createdatestr=createdate.toString();      ...
Read more