Use Advanced Settings for Performance and Customization

Use the Advanced settings under Content to access settings to Improve performance and customize certain behaviors.

1. In The Framework Admin Console select the Content tab.
2. On the Content Management page select your SQL Content Source.
3. Click the Advanced tab.
   
   
4. Cache Database:
   1. Select an alternate cache database to use.
   2. Changing this setting may require a complete refresh of sync jobs and a full crawl.
5. Filter Script:
   1. Enter the VB.NET Script to filter the items: return a boolean value. true = add, false = skip.
      

      Sample:

      if (flag = "bad") then
return false
else
return true
end if

6. Alternate Date Replace:
   1. Use to override the default way date parameters are passed to SQL.
   2. If your database doesn't support normal date type parameters, like some Db2 systems, specify a format to do perform a replacement with.
      Example: yyyy-MM-dd-HH.mm.ss.000000 .
      NOTE: Leave this field blank for default parameter functionality.
      
7. Change Log Entry Format:
   1. Use to override the change log entry format.
   2. If your connector uses both SPW_ID and SPW_SUBID for uniqueness (like ID and version) you can force SharePoint search to check for changes on all items with just the ID by changing the value to [SPW_ID].
      
8. Additional Changes SQL:
   1. Use this SQL Statement to load additional id's of items that have changed to increase crawl performance.
   2. This statement is ONLY called during incremental crawls.
      • Parameters
        • Required:
          • [SPW_ID] or @S_SPW_ID (for string) or @I_SPW_ID (for integer). 
          • [SPW_LASTUPATE] or [SPW_LASTUPATEUTC]
        • Optional:
          • [SPW_SUBID] or @S_SPW_SUBID (for string)
          • @I_SPW_SUBID (for integer)
            
            Sample SQL Statement (returns a list of IDs to be indexed):
   SELECT ID as SPW_ID, pid as SPW_SUBID from audittable where lastupdate > [SPW_LASTUPDATE]
9. Metadata Generation SQL:
   1.  Use this SQL Statement to override the generation of metadata on the metadata page.
   2.  This statement is ONLY called when you auto-generate the metadata.
      • Columns
        
        • Required: SPW_PROPERTY, SPW_COLUMN, SPW_COLTYPE ('T' = text, 'N' = float, 'I' = integer, 'D' = date, 'B' = boolean)
        • Optional: SPW_DESC, SPW_SCRIPT, SPW_MULTIFLAG ('T','F'), SPW_MULTIINDEX
10. Metadata Generation Script:
    1. Enter VBScript to override the auto generation of metadata, the above SQL, if present, is executed and provided as available dataset:

          HOST.GetDataSet() As DataSet HOST.AddStringMetadata(name As String,desc As String,scriptEnabled,columns As String,metascript As String) HOST.AddBooleanMetadata(name As String,desc As String,scriptEnabled,columns As
   String,metascript As String)
   HOST.AddNumberMetadata(name As String,desc As String,scriptEnabled,columns As String,metascript As String)
   HOST.AddIntegerMetadata(name As String,desc As String,scriptEnabled,columns As String,metascript As String)
   HOST.AddDateMetadata(name As String,desc As String,scriptEnabled,columns As String,metascript As String)

11. Script Library: Add VBScript functions to be used in all other scripts as library methods. See VB.Net Scripting
12. Purge Mode Only: Check to cause incremental crawls to remove only missing items from index. No other updates are performed.
    Note: This does not use the change log, so it may run slowly!
13. Click Save.