Hi all,
Today two tables in the same database ( which are the only ones with FTS in
that database) had FTS disabled. I know for sure that yesterday both of
them were enabled and working and nothing is showing in the logs about any
change to the status ( apart from the normal automatic PAUSE and RESUME of
indexing for the daily backup. ).
When I manually re-enabled each table the same message was created in the
logs:
"Changing the status to MERGE for the full-text catalog ".
Although everything is working now I am trying to track what could of caused
this.
Apart for purposely setting the table FTS disabled manually, what other
event could have caused the table's FTS become disabled?
Other databases in the same server had FTS on tables that weren't affected.
Thanks for the help.
Francisco
Oops,
Just to add this was on SQL 2005 sp1
Thanks.
"Francisco" <franciscousenet@.gmail.com> wrote in message
news:%23x$Xz7WNHHA.2232@.TK2MSFTNGP02.phx.gbl...
> Hi all,
> Today two tables in the same database ( which are the only ones with FTS
> in that database) had FTS disabled. I know for sure that yesterday both
> of them were enabled and working and nothing is showing in the logs about
> any change to the status ( apart from the normal automatic PAUSE and
> RESUME of indexing for the daily backup. ).
> When I manually re-enabled each table the same message was created in the
> logs:
> "Changing the status to MERGE for the full-text catalog ".
> Although everything is working now I am trying to track what could of
> caused this.
> Apart for purposely setting the table FTS disabled manually, what other
> event could have caused the table's FTS become disabled?
> Other databases in the same server had FTS on tables that weren't
> affected.
> Thanks for the help.
> Francisco
>
>
>
No comments:
Post a Comment