Re: Full-Text Catalog does not build...
From: Oleg Cherkasenko (oleg_at_opel.com.ua)
Date: 02/24/05
- Next message: Hilary Cotter: "Re: How to break the words"
- Previous message: John Kane: "Re: fulltext search not working"
- In reply to: John Kane: "Re: Full-Text Catalog does not build..."
- Next in thread: John Kane: "Re: Full-Text Catalog does not build..."
- Reply: John Kane: "Re: Full-Text Catalog does not build..."
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 24 Feb 2005 14:05:30 +0100
John, thank you.
By the way, from time to time during population I have got event about SQL
Server cant obtain LOCK.
Server machine has 6GB RAM, SQL Server uses AWE and has 5GB memory.
When can I read about languages were realized for FT in Yukon?
Are Vietnamese, Turkish, Arabic languages realized?
Its query output:
1.us_english
2.Microsoft SQL Server 2000 - 8.00.878 (Intel X86) Nov 11 2003 13:37:42
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
NT 5.0 (Build 2195: Service Pack 4)
3.default full-text language 0 2147483647 1033 1033
4.
5 cat_neu_prop1 F:\MSSQL\FTCatalog 9 1
6 cat_neu_preset F:\MSSQL\FTCatalog 0 1
7 cat_neu_x F:\MSSQL\FTCatalog 1 1
5.
dbo presets PK_presets 1 1 cat_neu_preset
dbo properties PK_properties 7 1 cat_neu_prop1
dbo xproperties_string PK_xproperties_string 1 1 cat_neu_x
6.
dbo 1310627712 presets name 3 NULL NULL 0
dbo 521768916 properties string_value 4 NULL NULL 0
dbo 521768916 properties text_value 5 NULL NULL 0
dbo 2070298435 xproperties_string string_value 2 NULL NULL 0
7.
properties dbo user table 2003-11-17 18:46:50.360
8.
object_id uniqueidentifier no 16 no (n/a) (n/a) NULL
descriptor_id uniqueidentifier no 16 no (n/a) (n/a) NULL
value sql_variant no 8016 yes no (n/a) NULL
string_value nvarchar no 7000 yes (n/a) (n/a)
SQL_Latin1_General_CP1_CI_AS
text_value ntext no 16 yes (n/a) (n/a)
SQL_Latin1_General_CP1_CI_AS
preset_id uniqueidentifier no 16 yes (n/a) (n/a) NULL
id timestamp no 8 no (n/a) (n/a) NULL
9.
No identity column defined. NULL NULL NULL
10.
No rowguidcol column defined.
11.
PRIMARY
12.
IX_properties_descriptor_id nonclustered located on PRIMARY descriptor_id
IX_properties_object_id nonclustered located on PRIMARY object_id
IX_properties_object_id_descriptor_id nonclustered, unique located on
PRIMARY object_id, descriptor_id
PK_properties clustered, unique, primary key located on PRIMARY id
13.
FOREIGN KEY FK_properties_descriptors Cascade No Action Enabled
Is_For_Replication descriptor_id
REFERENCES mtn_virgin.dbo.descriptors (id)
FOREIGN KEY FK_properties_nodes No Action No Action Disabled
Is_For_Replication object_id
REFERENCES mtn_virgin.dbo.nodes (id)
PRIMARY KEY (clustered) PK_properties (n/a) (n/a) (n/a) (n/a) id
Regards,
Oleg Cherkasenko.
"John Kane" <jt-kane@comcast.net> wrote in message
news:ODKi1VcGFHA.2736@TK2MSFTNGP12.phx.gbl...
> Oleg,
> Could you post the full output of the below SQL code as this is most
> helpful
> information in troubleshooting SQL FTS issues.
>
> use <your_database_name_here>
> go
> SELECT @@language
> SELECT @@version
> sp_configure 'default full-text language'
> EXEC sp_help_fulltext_catalogs
> EXEC sp_help_fulltext_tables
> EXEC sp_help_fulltext_columns
> EXEC sp_help <your_FT-enable_table_name_here>
> go
>
> You should also review all the KB articles and white paper at "SQL Server
> 2000 Full-Text Search Resources and Links" at:
> http://spaces.msn.com/members/jtkane/Blog/cns!1pWDBCiDX1uvH5ATJmNCVLPQ!305.entry
>
> I'd also highly recommend that you consider upgrading to SQL Server 2005
> (Yukon) as a FT Indexed table of 120 million rows is well above the upper
> tested limits of SQL Server 2000. While SQL Server 2005 is still in beta
> (currently Beta2, but a more public Beta3 is due out soon), it has many
> Full
> Text Indexing performance improvements and has been tested with tables
> well
> above 120 million rows.
>
> Finally, when Full Population fails to complete or appears to 'hang', the
> first place you should look is the server's Application event log as this
> is
> the only place where such errors are written. You should review all
> "Microsoft Search" and MssCi source events (errors, warnings AND
> informationals) and especially MssCi events as most likely the FT Catalog
> is
> corrupt and the MSSearch service has paused the FT Indexing. Note, the FT
> Indexing of a table size of 120 million rows in SQL Server 2000 can take
> several weeks to complete successfully.
>
> Regards,
> John
> --
> SQL Full Text Search Blog
> http://spaces.msn.com/members/jtkane/
>
>
> "news.microsoft.com" <oleg@opel.com.ua> wrote in message
> news:eZ7NP4bGFHA.576@TK2MSFTNGP15.phx.gbl...
>> Hello All,
>> Database size=150 GB
>> FT indexed Table = 120 millions of records.
>>
>> On the start of project database was small and FT catalog builds
>> successfully.
>> Now building and populating can not finish. The status of FTC is:
> Populating
>> in progress, may be paused, but not Idle.
>>
>> I see this 3 weeks.
>>
>> What can I do?
>>
>> Thank you.
>>
>>
>
>
- Next message: Hilary Cotter: "Re: How to break the words"
- Previous message: John Kane: "Re: fulltext search not working"
- In reply to: John Kane: "Re: Full-Text Catalog does not build..."
- Next in thread: John Kane: "Re: Full-Text Catalog does not build..."
- Reply: John Kane: "Re: Full-Text Catalog does not build..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
