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
The directory is FTDATA, no subdirectories. I have tried in a nonclustered
server too, whit the same result. Could you help me?
"Hilary Cotter" wrote:
> 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.
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
>
http://www.nwsu.com/0974973602.html >
>
> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
> news:%238ZUxJKoEHA.2340@TK2MSFTNGP11.phx.gbl...
> > 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.
> >
> > --
> > Hilary Cotter
> > Looking for a SQL Server replication book?
> >
http://www.nwsu.com/0974973602.html > >
> >
> > "qwalgrande" <qwalgrande*nospam*@yahoo.es> wrote in message
> > news:6131ACD4-A717-48D6-AC63-4F2FE43B7CA5@microsoft.com...
> > > 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?
> > >
> > > --
> > > qwalgrande
> >
> >
>
>
