> We recently created a table with an FTI in a database, then created a
> view to this table in another database. We found we were not able to
> access the FTI using CONTAINS through the view.
>
> We got round it by changing our SP to use the FQN instead of the view,
> but it was of interest that the view method didn't work.
> Feature/bug??
>

"MrTim" <MrTim@discussions.microsoft.com> wrote in message
news:BDCF62C4-4657-4C36-BD33-893679B18F80@microsoft.com...
> We recently created a table with an FTI in a database, then created a view
> to
> this table in another database. We found we were not able to access the
> FTI
> using CONTAINS through the view.
>
> We got round it by changing our SP to use the FQN instead of the view, but
> it was of interest that the view method didn't work. Feature/bug??

"Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
news:%23avLUtvsGHA.4420@TK2MSFTNGP04.phx.gbl...
> I'm confused. I can get this to work. In pubs, FTI the au_lname column in
> authors table, then in northwinds create this view
>
> use northwind
> GO
> create view test
> as
> select * from pubs.dbo.authors where contains(*,'ringer')
> GO
> create view test1
> as
> select * from pubs.dbo.authors
> join (select * from containstable(pubs.dbo.authors,*,'ringer')) as x
> on x.[key]=pubs.dbo.authors.au_id
> GO
> select * from test
> --two rows returned.
> select * from test1
> --two rows returned.
>
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
>
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
>
> 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
>
>
>
> "MrTim" <MrTim@discussions.microsoft.com> wrote in message
> news:BDCF62C4-4657-4C36-BD33-893679B18F80@microsoft.com...
>> We recently created a table with an FTI in a database, then created a
>> view to
>> this table in another database. We found we were not able to access the
>> FTI
>> using CONTAINS through the view.
>>
>> We got round it by changing our SP to use the FQN instead of the view,
>> but
>> it was of interest that the view method didn't work. Feature/bug??
>
>

"Daniel Crichton" <msnews@worldofspack.com> wrote in message
news:%23HHNwkJtGHA.3264@TK2MSFTNGP03.phx.gbl...
> Hilary, I think he meant doing something like this:
>
> create view test1 as
> select * from pubs.dbo.authors
> go
>
> select * from test1 where contains(*,'ringer')
>
> which won't work because the FTI is on the base table, not on the view.
>
> Dan
>
>
> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
> news:%23avLUtvsGHA.4420@TK2MSFTNGP04.phx.gbl...
>> I'm confused. I can get this to work. In pubs, FTI the au_lname column in
>> authors table, then in northwinds create this view
>>
>> use northwind
>> GO
>> create view test
>> as
>> select * from pubs.dbo.authors where contains(*,'ringer')
>> GO
>> create view test1
>> as
>> select * from pubs.dbo.authors
>> join (select * from containstable(pubs.dbo.authors,*,'ringer')) as x
>> on x.[key]=pubs.dbo.authors.au_id
>> GO
>> select * from test
>> --two rows returned.
>> select * from test1
>> --two rows returned.
>>
>> --
>> Hilary Cotter
>> Director of Text Mining and Database Strategy
>> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
>>
>> This posting is my own and doesn't necessarily represent RelevantNoise's
>> positions, strategies or opinions.
>>
>> 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
>>
>>
>>
>> "MrTim" <MrTim@discussions.microsoft.com> wrote in message
>> news:BDCF62C4-4657-4C36-BD33-893679B18F80@microsoft.com...
>>> We recently created a table with an FTI in a database, then created a
>>> view to
>>> this table in another database. We found we were not able to access the
>>> FTI
>>> using CONTAINS through the view.
>>>
>>> We got round it by changing our SP to use the FQN instead of the view,
>>> but
>>> it was of interest that the view method didn't work. Feature/bug??
>>
>>
>
>