Expand News
IS Administration
Expand MMC
Expand Com Objects
Expand IDA/IDQ
IS Programming
Expand IS Programming
IS TroubleShooting
Expand Indexing
Expand Querying
IS Optimizing
Expand Querying
Expand Indexing
IS Links
Expand MSDN
Expand TechNet
Expand Other MS
Expand Other Links
Expand iFilters
SQL 2000 FTS
Expand Loading Data
Expand Indexing
Using the Wizard
Expand Querying
Expand SQL FTS Links
SQL 2005 FTS
Expand What's New

Index Server Faq

Using the Microsoft SQL FTS Wizard when the Full-Text Index Table menu item is disabled

There can be serveral causes of the Full-Text Index Table menu option not being enables

  • SQL FTS is not enabled on this SQL server. Click here for instructions on how to install SQL FTS on your SQL Server.

  • You are not in the dbo role for this database

  • The System Administrator role is not in the Local Administrators group for this machine or the NTAuthority\Logon group is not in the System Administrators group.

    Thanks to Phillip Schmidt [PSchmidt_Don'tSpamMe@hdrinc.com] for pointing this out to me: If you remove BUILTIN\Administrators and Full Text is enabled, add a login account for the Local System account using sp_grantlogin [NT Authority\System], and ensure that the login account is a member of the sysadmin fixed server role. Here is some sample TSQL code to do this:

    if not exists (select * from master.dbo.syslogins where loginname = N'NT Authority\System')

    exec sp_grantlogin N'NT Authority\System'

    exec sp_defaultdb N'NT Authority\System', N'master'

    exec sp_defaultlanguage N'NT Authority\System', N'us_english'


    exec sp_addsrvrolemember N'NT Authority\System', sysadmin


  • Something else yet undetermined. Microsoft acknowledges this problem in this kb article and recommends that you use the full text stored procedures to manage your catalog or tables.

    When I run across this problem (I don't run across is often as typically I use the full text stored procedures) I normally use the SQLFTSWiz.exe program which can be found by default in: C:\Program Files\Microsoft SQL Server\80\Tools\Binn you can launch it by opening a command prompt and typing for NT Authentication:

    sqlftwiz /n /sSQLServerName[\InstanceName] /dpubs

    or for SQL Authentication:

    sqlftwiz /sSQLServerName[\InstanceName] /dpubs /uAccount /pPassword

    In both of the above examples, SQLServerName[\InstanceName] is the name of the SQL Server you wish to connect to. If you are using the default instance you would use the below:

    sqlftwiz /sSQLServerName /dpubs /uAccount /pPassword

    If you are using an instance, other than the default instance you would use the below (where InstanceName is the name of the instance you are using):

    sqlftwiz /sSQLServerName\InstanceName /dpubs /uAccount /pPassword

    Pubs is the database you wish to create your full text table in.

    The dialogs you get are for the most part identical to the dialogs you would get if you were to just right click on a table.

    This is the initial splash screen. Click Next to launch the table selection dialog box (Figure 2).

    Figure 1.

    Clicking Next will launch the select tables dialog box as illustrated in Figure 2.

    Figure 2. In this drop down box, select the table you wish to index. Only user tables will drop down up in the drop down list. You can't index system tables. Click Next to launch the Select an Index dialog box (Figure 3).

    Figure 3.

    If there is more than one unique index on the table you will have the option to select the index you want to use. You should pick an index which is not updated. Click on Next to launch the Select Table Columns dialog box (Figure 4).

    Figure 4.

    Click on the check boxes to the left of the tables to index the tables. In the Word Breaker drop down box, select the language word breaker you wish to use to index your content. Notice that the Spanish word breaker is not present in the drop down list. To index a column in a table using the Spanish word breaker you must use the TSQL commands. Click here for an example of the commands .

    If you want to index content natively (ie, a word document without having to convert it to text) and that content is stored in an Image data type column, you can select the document type column which is a column (char(4)) which will contain the extension of the native content stored in the Image data type column. For example if you were storing PDFs (Adobe Acrobat files) in this column the values of the document type column would be .PDF. You can store different types of data in the Image data type column (ie Word Documents, PDFs, Tiffs, etc) and have the corresponding extensions stored in the document type column so the correct iFilter would be applied to the content. Figure 5 illustrates how you would select the document type column.

    Figure 5. Click on Next to Select a Catalog (Figure 6).

    Figure 6.

    Figure 7.

    Figure 8.

    Figure 9.

    Figure 10.


    designed by :: smilla group