full-text index with multiple tables

Hi All: I just stumbled across this post, noting that you can create a view
against multiple tables, and then use the view in the full-text index, so
that if you do a freetexttable query agains the view, you are in effect
searching multiple tables simulataneously.

http://versia.com/2008/02/06/sql-server-full-text-searching-across-mul...le-tabl

This may be old news already, but I had previously been doing nested queries
against each table in the full-text index...this seems much more
straightforward...just curious if there are any problems or issues with this
method?

"geekyguy" wrote in message

> Hi All: I just stumbled across this post, noting that you can create a
> view against multiple tables, and then use the view in the full-text
> index, so that if you do a freetexttable query agains the view, you are in
> effect searching multiple tables simulataneously.
>
> http://versia.com/2008/02/06/sql-server-full-text-searching-across-mul...le-tabl
>
> This may be old news already, but I had previously been doing nested
> queries against each table in the full-text index...this seems much more
> straightforward...just curious if there are any problems or issues with
> this method?
>
OK, I ran into my first problem...after creating this view, I attempted to
update one of the tables that has a field in the view, I'm getting an error:

"UPDATE failed because the following SET options have incorrect settings:
'ARITHABORT'. Verify that SET options are correct for use with indexed views
and/or indexes on computed columns and/or query notifications and/or xml
data type methods."

Do I need to change the update statement to "set arithabort on" or does this
create a problem with the view? How do I set arithabort to "on" within the
context of an update statement