Feedback on CHANGE TRACKING with SCHEDULE

Hi,
I am searching concrete feedback on SQL Server 2000 SP3 Server
that have in place FTS catalog population with the following options:
- CHANGE TRACKING
- SCHEDULE
Many thanks.
Change tracking with update index in background will continually poll the tables which you are full text indexing and index changes.
Some business requirements require that you update the index at discrete intervals; ie once a minute, hour, day. There are normally two reasons for this 1) performance, 2) recovery.
You may get better performance on heavily updated tables by scheduling the indexing of the changes. For recovery, sometimes you need to synchronize your catalog updates with backups, transaction log dumps etc. There have also been problems with clustering and change tracking, where you failover to a new node, and suddenly your catalog is read only - ie subsequent updates are not processed. With update index at scheduled intervals this problem can be avoided.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Jean-Marc Pugin" <jmpugin@.mobileworkers.com> wrote in message news:Owl82rc3EHA.2804@.TK2MSFTNGP15.phx.gbl...
Hi,
I am searching concrete feedback on SQL Server 2000 SP3 Server
that have in place FTS catalog population with the following options:
- CHANGE TRACKING
- SCHEDULE
Many thanks.
|||Hi,
I have seen that during schedule definition you can define the starting
hour.
Is it possible to define a Time Interval during which catalog update
will occur i.e. only from 2 to 3 AM.
It is because on a Production Server those heavy computations are better
achieved during batch windows.
Thanks
_____
From: Hilary Cotter [mailto:hilary.cotter@.gmail.com]
Posted At: jeudi 9 dcembre 2004 13:46
Posted To: microsoft.public.sqlserver.fulltext
Conversation: Feedback on CHANGE TRACKING with SCHEDULE
Subject: Re: Feedback on CHANGE TRACKING with SCHEDULE
Change tracking with update index in background will continually poll
the tables which you are full text indexing and index changes.
Some business requirements require that you update the index at discrete
intervals; ie once a minute, hour, day. There are normally two reasons
for this 1) performance, 2) recovery.
You may get better performance on heavily updated tables by scheduling
the indexing of the changes. For recovery, sometimes you need to
synchronize your catalog updates with backups, transaction log dumps
etc. There have also been problems with clustering and change tracking,
where you failover to a new node, and suddenly your catalog is read only
- ie subsequent updates are not processed. With update index at
scheduled intervals this problem can be avoided.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Jean-Marc Pugin" <jmpugin@.mobileworkers.com> wrote in message
news:Owl82rc3EHA.2804@.TK2MSFTNGP15.phx.gbl...
Hi,
I am searching concrete feedback on SQL Server 2000 SP3 Server
that have in place FTS catalog population with the following options:
- CHANGE TRACKING
- SCHEDULE
Many thanks.
|||It is. Right click on your table, select Full Text Index Table, select change tracking, then right click on your table again, and Full Text Index Table, and schedules. Select New Table Schedule, Update Index, Reoccuring, occurs every 1 hour, and then fill in 2 for the starting time and 3 for the ending time.
This will do a single update index of all the changes tracked for the entire day.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Jean-Marc Pugin" <jmpugin@.mobileworkers.com> wrote in message news:eMOncPf3EHA.1396@.tk2msftngp13.phx.gbl...
Hi,
I have seen that during schedule definition you can define the starting hour.
Is it possible to define a Time Interval during which catalog update will occur i.e. only from 2 to 3 AM.
It is because on a Production Server those heavy computations are better achieved during batch windows.
Thanks

From: Hilary Cotter [mailto:hilary.cotter@.gmail.com]
Posted At: jeudi 9 dcembre 2004 13:46
Posted To: microsoft.public.sqlserver.fulltext
Conversation: Feedback on CHANGE TRACKING with SCHEDULE
Subject: Re: Feedback on CHANGE TRACKING with SCHEDULE
Change tracking with update index in background will continually poll the tables which you are full text indexing and index changes.
Some business requirements require that you update the index at discrete intervals; ie once a minute, hour, day. There are normally two reasons for this 1) performance, 2) recovery.
You may get better performance on heavily updated tables by scheduling the indexing of the changes. For recovery, sometimes you need to synchronize your catalog updates with backups, transaction log dumps etc. There have also been problems with clustering and change tracking, where you failover to a new node, and suddenly your catalog is read only - ie subsequent updates are not processed. With update index at scheduled intervals this problem can be avoided.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Jean-Marc Pugin" <jmpugin@.mobileworkers.com> wrote in message news:Owl82rc3EHA.2804@.TK2MSFTNGP15.phx.gbl...
Hi,
I am searching concrete feedback on SQL Server 2000 SP3 Server
that have in place FTS catalog population with the following options:
- CHANGE TRACKING
- SCHEDULE
Many thanks.