Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Full-Text Search / September 2004

Tip: Looking for answers? Try searching our database.

Incremental Fill of Full-Text Catalog Problem. Please help!

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Jos? Fern?ndez - 20 Sep 2004 09:06 GMT
Hello everybody, and thanks in advance for your help.

Well, I have created a full-text index in a table with about one
million
records, indexing three fields.
To start with, I created it with an incremental filling programming
once
a week, saturday night.
But the problem is that without an apparent cause, an incremental
filling
of the catalog happens now and then, in short intervals, wich are in
no way
regular (the database is not manipulated nor any information added,
deleted or modified for the MSSearch to re-index)
I re-created the full-text index without any filling programming, and
it
continues going on with the incremental fillings.
What could be the cause? Any idea on how can I avoid these fillings
that seem
to happen randomly?
Please, help me.

Thank you very much again.
Jose.
Hilary Cotter - 20 Sep 2004 13:35 GMT
Hola Jose!

The English word for filling is population. From what you describe it sounds
like you are getting random incremental populations.

Can you verify 1) that there is a timestamp column on the tables you are
Full Text indexing? This will ensure that an incremental population is being
done as opposed to a full population. Your first population will always be a
full population.

2) can you issue this query on the server you are full text indexing?

select name from msdb.dbo.sysjobsteps, sysjobs where command like
'%sp_fulltext%'
and sysjobs.job_id=sysjobsteps.job_id

This will give you the names of population jobs. Check the management folder
to see if the jobs with these names have any schedules on them.

This could account for these un anticipated schedules.

Signature

Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

> Hello everybody, and thanks in advance for your help.
>
[quoted text clipped - 20 lines]
> Thank you very much again.
> Jose.
John Kane - 23 Sep 2004 08:39 GMT
Jose,
Could you provide additional information on what version of SQL Server (7.0
or 2000) you are using via -- SELECT @@version -- as this is very helpful in
understanding your environment.

If you are using SQL Server 2000, you can enable "Change Tracking" and
"Update Index in Background" and avoid the need to ever have to run a
scheduled Incremental Population (or filling of the catalog). SQL Server
2000 Books Online (BOL) has the details on how to implement "Change
Tracking" and "Update Index in Background".

Regards,
John

> Hello everybody, and thanks in advance for your help.
>
[quoted text clipped - 20 lines]
> Thank you very much again.
> Jose.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.