Hi,
I have a SQL Server 2000 cluster, sp 3 in w2k.
When the catalog is reindexed, some documents appears in FTDATA folder. If I
delete the documents, then they reappear in the next indexing.
I'm thinking about to schedule a batch that cleanup this folder, because I
have the FTDATA in the Quorum drive, with no much free space.
Why this is? How can I avoid it?

Signature
qwalgrande
Hilary Cotter - 22 Sep 2004 13:47 GMT
What do you mean by documents? Can you open these documents in Word or
notepad?
These documents will be extracted by the indexing process, but on my non
clustered system they are cleaned up.
Some files will remain which are used my mssearch to track where it is in
the indexing process. You shouldn't touch these files.

Signature
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
> Hi,
>
[quoted text clipped - 7 lines]
>
> Why this is? How can I avoid it?
Hilary Cotter - 22 Sep 2004 14:04 GMT
one more point - exactly which subdirectory of ftdata do these files exist
in.
It could be possible that they are eithre configuration files or the actual
index/catalog files themselves.

Signature
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
> What do you mean by documents? Can you open these documents in Word or
> notepad?
[quoted text clipped - 17 lines]
> >
> > Why this is? How can I avoid it?
qwalgrande - 22 Sep 2004 15:53 GMT
Hello, Hilary.
I will try to explain it better. These "documents" are the documents that I
had inserted in my indexed image column. In the population, the documents
"pass" for the folder and quickly disappear, but a few documents stay in the
folder and don't cleaned up.
The directory is FTDATA, no subdirectories. I have tried in a nonclustered
server too, whit the same result. Could you help me?
Thanks in advanced.
> one more point - exactly which subdirectory of ftdata do these files exist
> in.
[quoted text clipped - 25 lines]
> > >
> > > Why this is? How can I avoid it?