Article ID: 308841
Article Last Modified on 4/12/2006
APPLIES TO
- Microsoft SQL Server 2000 Standard Edition
This article was previously published under Q308841
BUG #: 355180 (SHILOH_BUGS)
SYMPTOMS
If you use the entire filename, and not just the extension, of a file to specify the type of document stored in a full-text enabled column, the data returned when SQL Server queries the full-text index, may not be consistent with the data actually stored in the column. The following code shows how you can use the filename to specify the type of document stored:
exec sp_fulltext_column 'BlobTestTbl', 'Document', 'add', NULL, 'Filename'
In the preceding code, the fifth argument Filename is the name of the column that stores the type of document. In this case, the entire filename is stored in the Filename column.
According to SQL Server Books Online, this fifth argument must point to a column that stores the extension of the document stored in the full-text enabled column. For more information, see the "Filtering Supported File Types" topic in SQL Server Books Online.
In addition, the following errors may appear in the Microsoft Windows NT Application Log if you attempt to enable the column for full-text indexing:
RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
WORKAROUND
To work around this problem, make sure that only the extension is stored in the column that specifies the type of document stored in a full-text index. For example, you use the .doc extension for a Microsoft Word document.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.
Keywords: kbbug kbfix KB308841