Re: FT Catalog "optimise" or "populate" differences
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Fri, 19 Oct 2007 09:44:57 -0400
Population is where you get all the data from your tables and full-text
index it.
Optimization is where you consolidate the numerous indexes that may form as
the result of an indexing operation for a table into one index. Normally
this is forced every 50,000 rows. With change tracking you can get
significant fragmentation of your full-text indexes.
--
RelevantNoise.com - dedicated to mining blogs for business intelligence.
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
"Nick Gilbert" <nickg@xxxxxxxxxxxxxxxx> wrote in message
news:OD6Qg$jEIHA.5044@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
In SQL 2005 does anyone know what the difference between a full text
catalogue "optimize" and a "populate" is? In 2000 I think there was only
populate.
It seems you can't schedule a normal "populate" in 2005 - only an
"optimise".
Nick...
.
- Follow-Ups:
- Re: FT Catalog "optimise" or "populate" differences
- From: Nick Gilbert
- Re: FT Catalog "optimise" or "populate" differences
- References:
- FT Catalog "optimise" or "populate" differences
- From: Nick Gilbert
- FT Catalog "optimise" or "populate" differences
- Prev by Date: Re: full text update
- Next by Date: Major full-text related problem!
- Previous by thread: FT Catalog "optimise" or "populate" differences
- Next by thread: Re: FT Catalog "optimise" or "populate" differences
- Index(es):