Full Text Index on Table Versus View
-
Monday, March 12, 2012 11:59 AM
Hello all,
we know that FTI can be created at a table or view level as long as prerequisites are satisfified.
I have a requirement to implement FTS on multiple identical tables(table parttioning) for a given FTS query.
I can think of three possible solutions as of now.
1.Create FTI on each individual table and then write FTS query against each table with union all to get the final results.
2.Create FTI on a single view which selects data from all tables using Union all.
3.Create FTI against each view created one for each base table and then issue FTS query against all views with Union all.
I came to know that there are lot of restrictions on view definition while creating FTI on it like schema binding, schema.table name, restriction of few SQl caluses like table hints, Union All, Min,MAx,Top,Ouer join queries.
So i am thinking solution 2 may not be possible.
Can somebody suggest when to create FTI on table vs view and pros and cons?
Can somebody suggest any better approach for this kind of scenario?
Thanks
Samba
- Edited by Sambasiva Reddy Monday, March 12, 2012 12:00 PM
- Edited by Sambasiva Reddy Monday, March 12, 2012 12:07 PM
All Replies
-
Wednesday, March 14, 2012 7:29 AMi think either option 1 or 2 is ok
smiling~
-
Saturday, March 24, 2012 5:12 AM
-
Monday, March 26, 2012 11:45 AM
Hello,
Follow the links below. It will help you.
http://blog.sqlauthority.com/2008/09/05/sql-server-creating-full-text-catalog-and-index/
http://www.simple-talk.com/sql/learn-sql-server/understanding-full-text-indexing-in-sql-server/
http://msdn.microsoft.com/en-us/library/ms187317.aspx

