Hi Thad, short answer is you're screwed. I've been fighting this for months. There is an FTS fortification available if you're on the right version. See the link in my post I put up about 30-45 mins ago. Hope this helps - Jase
> On Feb 17, 2015, at 5:07 PM, Thad Esser <[email protected]> wrote: > > ** > Hello, > > I find myself in a situation where I have an FTS reindex in progress that I > don't think will be complete by this weekend, which is when our database > server will be restarted. Due to other circumstances, I can't stop the > rebooting of the database server. > * How will this impact the FTS reindex if it is still in progress? > * Will the reindexing pick up where it left off once the DB connection is > re-established? (the AR Server usually recovers just fine these days) > * Would shutting down the AR Server first make things worse, or better (in > terms of the re-indexing operations)? > * Are there any preventative steps I can take to keep the FTS index from > becoming corrupted (which seems to happen really easily and is my main > concern)? > * Or am I just screwed, and am going to have to restart the FTS indexing > again after the DB reboot? > > Thanks, > Thad > > Environment: ARS 8.1.0 on Windows with a remote SQL Server 2008 DB. Full 8.1 > ITSM suite. > _ARSlist: "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"
