On a previous version of FTS, I seem to recall there was a table you could query that would let you know what fields were indexed. It's either in the docs or in the online knowledge base, I bet.
Also, in my limited experience (which may not apply to your situation), it seemed that rebuilding the indexes was faster than actually trying to reindex. I was on Oracle, and that was ARS 6.0 or 7.5 at the time, with maybe 250,000 records, include 2 or 3 diary fields & a 0 length character field plus some smaller character fields. Directions for that were also in the knowledge base. David Durling University of Georgia > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG] On Behalf Of Tauf Chowdhury > Sent: Tuesday, May 28, 2013 1:54 PM > To: arslist@ARSLIST.ORG > Subject: Re: how to identify FTS-indexed fields from the DB? > > I may be fuzzy on this but there is a table called FT_Pending that holds some > data on what is being indexed and then dropped once it is in the collection > directory. If your indexing is running for more than a month though, I'm > pretty sure it's hung and not doing anything. The size of FT_Pending should > always be small if the indexing is in progress. > > Sent from my iPhone > > On May 28, 2013, at 1:47 PM, Andrew Hicox <and...@hicox.com> wrote: > > > Hello everyone, > > > > I currently find myself in the third circle of ARS hell ... debugging FTS > > on ARS > 7.6.03 (it's a long story on why we're not on 7.6.04 yet, but suffice it to > say, I > have no immediate control of that situation). > > > > We have had an FTS re-index procedure running for more than a month > now. I need to get an idea on where it is, and how much longer it needs to > finish. I can trace some of this through the arftsindex.log(s). It seems to > iterate per-form, per-indexed field. So ... form A, indexed field 1 ... then > indexed field 2, etc, etc cycling through every record in the form N times > where N is the number of indexed columns in the form. > > > > So ... part of this is that I need to be able to know exactly how many such > fields and forms I'm looking at. > > I need a better way of doing this than to open each form on the server, and > pick through the field properties on every form. > > > > I've tried running the sql log on server startup to try and capture whatever > it is the ft dispatcher executes in the DB to find the indexed fields, but if > it's > there I sure as heck can't find it. There do not appear to be any obvious > columns on the 'FIELD' table that would indicate FTS indexing mode, nor do > there appear to be any adjunct tables (like the various FIELD_* tables) that > would contain this data. > > > > I'd like very much to be able to execute a query on the DB that would > return schemaid and fieldid of all the fields that the FTS indexer is going > to try > and run through. > > > > Does anyone know of a way to do this? > > > > -Andy > > > __________________________________________________________ > ____________ > > _________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > > "Where the Answers Are, and have been for 20 years" > > __________________________________________________________ > _____________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the > Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
