 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / Other Technologies / Full-Text Search / January 2007Are Population Schedules required?
Hi All: I have an FT Cat with 3 tables in it that I created 6 months ago. Each table in the FT Cat has "track changes" set to "automatic" There's no defined population schedule. Will this catalog be updated automatically when the data in the tables changes, or does it require a population schedule to regularly refresh the FT Catalog? TIA It will be updated within seconds - change tracking updates the index near real time.  SignatureHilary Cotter 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 All: I have an FT Cat with 3 tables in it that I created 6 months ago. > [quoted text clipped - 7 lines] > > TIA Thanks Hilary! So, just for my edification, what are population schedules for? For very large cats & datasets where you would NOT want it automatically updating, but would want to schedule repopulation say once daily at 3 am? > It will be updated within seconds - change tracking updates the index near > real time. [quoted text clipped - 10 lines] >> >> TIA Hello geek-y-guy, Historically in SQL 2000, populations could impact querying (errors occurring) so you may have wanted to do delay the population. If you have lots of changes you may still want to delay population to avoid the performance hit of population and querying Simon Sabin SQL Server MVP http://sqlblogcasts.com/blogs/simons > Thanks Hilary! > > So, just for my edification, what are population schedules for? For > very large cats & datasets where you would NOT want it automatically > updating, but would want to schedule repopulation say once daily at 3 > am? In general you should always use change tracking as it offers best performance and near real time indexing. If you select manual change tracking you can update the index during quiet times or in batches to minimize the impact of locking during indexing. There are two other indexing options: full-populations and incremental populations. If the bulk of your data changes in regular patterns you might want to schedule a full-population. Incremental populations work best when a smaller portion of your data changes at a time. In this case you could schedule an incremental population. As change tracking can lead to some fragmentation you might want to schedule the reorganization of your catalog. SignatureHilary Cotter 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 > Thanks Hilary! > [quoted text clipped - 17 lines] >>> >>> TIA |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.