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.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html [quoted text, click to view] "Jos? Fern?ndez" <regjose11@hotmail.com> wrote in message
news:4ab097a2.0409200006.6f65ef06@posting.google.com...
> 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.