Full text index not tracking changes on an indexed view

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

mbedser@gmail.com - 27 Jul 2007 17:54 GMT

We had a peculiar situation today where our lovely indexed view
obviously had textual data in it but some recently added rows were not
being returned in a CONTAINS query when they should have been.
Deleting and recreating the FT index fixed things immediately and I
can't seem to reproduce it but it worries me for our live deployment
(due imminently!).

Has anyone else seen this? Is it reproducible (and fixable?!)

Mark

Reply to this Message

Jean-Pierre Riehl - 28 Jul 2007 15:00 GMT

Hi Mark,

Do you have a timestamp column in underlaying table(s) ?
Have you activated automatic change tracking for your index ?

Signature

Jean-Pierre Riehl
http://blog.djeepy1.net
http://www.bewise.fr

> We had a peculiar situation today where our lovely indexed view
> obviously had textual data in it but some recently added rows were not
[quoted text clipped - 6 lines]
>
> Mark

Reply to this Message

Hilary Cotter - 28 Jul 2007 17:12 GMT

Change tracking does not require a timestamp column.

I think your problem will be solved if you do use change tracking (as the
previous poster points out).

Signature

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

> Hi Mark,
>
[quoted text clipped - 11 lines]
>>
>> Mark

Reply to this Message

Jean-Pierre Riehl - 29 Jul 2007 16:48 GMT

I apologize for my mistake. Incremental update requires a timestamp column
whereas change tracking doesn't.

Signature

Jean-Pierre Riehl
http://blog.djeepy1.net
http://www.bewise.fr

> Change tracking does not require a timestamp column.
>
[quoted text clipped - 16 lines]
>>>
>>> Mark

Reply to this Message