Shank,
See inline comments below, starting with [jtkane].
Thanks,
John
[quoted text, click to view] "shank" <shank@tampabay.rr.com> wrote in message
news:#19IgyDsDHA.2060@TK2MSFTNGP10.phx.gbl...
> >>A table's full text index can only be stored in a single catalog,<<
> I need clarification on this. I have 3 tables that have searchable
> information.
>
> 1) How do I get 3 table's columns into one catalog? If I had access to the
> server I'm sure it would be a simple query. But I'm dealing with a web
host
> and shared server. Can a catalog be based upon a store procedure? I could
> build the SP myself then.
[jtkane] - Easy, you create one FT Catalog, for example named
"My_FT_Catalog" and then you can add or place all three tables into the one
FT Catalog "My_FT_Catalog", for example:
sp_fulltext_table '<My_FT_Table_name>', 'create', 'My_FT_Catalog',
'<My_FT_Table_name_Unique_Index>'
Yes, you can create a catalog based upon a stored procedure, however, you
will need to proceed each system stored proc sp_fulltext* with an EXEC.
[quoted text, click to view] > 2) Does FREETEXT only work with catalogs? Could I create my own table as a
> pseudo-catalog of sorts?
[jtkane] - Yes, you must create and then populate a Full-Text Catalog prior
to using FREETEXT.
I can't be the only one that's ever had this problem.
[jtkane] - True!
[quoted text, click to view] > thanks!
>
>
> "Hilary Cotter" <hilaryK@att.net> wrote in message
> news:31fa01c3b039$52f57bb0$a601280a@phx.gbl...
> > FreeText is Microsoft's preferred way of searching. They
> > consider it to be the natural way to search. Contains can
> > be faster, but you have to deal with the annoying noise
> > word error, and it is a very strict search. Freetext is
> > fuzzy and the biggest complaint about it, it that it
> > returns too many hits.
> >
> > Google does a Contains based search, which works best for
> > them as they are indexing the internet. For enterprise
> > searching your choice will depend on your needs and the
> > amount of your content. In general the more content the
> > more likely Contains will work for you. You will have to
> > see what works out best for you.
> >
> > A table's full text index can only be stored in a single
> > catalog, no matter how many columns you have. your isp
> > will have to create a single catalog.
> > >-----Original Message-----
> > >I have 3 tables....
> > >Main table is [Stock] which contains columns [ItemNo],
> > [Description],
> > >[Type], and other columns..
> > >1st Related table is [Songs] which contains columns
> > [ItemNo], [SongTitles],
> > >[Singers], and other columns..
> > >2nd Related table is [Equipment] which contains columns
> > [ItemNo],
> > >[Features], [Specs], and other columns..
> > >They're related on the [ItemNo] field.
> > >
> > >I want users to have one search box to enter any words or
> > phrases they
> > >choose to search upon all of the above fields. What is
> > the best way to do
> > >this? I'm guessing FREETEXT and a catalog is the answer.
> > My problem with
> > >this is (a) I don't have SQL Server locally. I'm on a
> > shared server and
> > >don't have the luxury of trying
> > >different options. My host has to create the catalogs.
> > And (b) how do I ask
> > >my host to create one catalog containing all the above
> > fields? Is there a
> > >way that I can do this?
> > >
> > >I would expect my results to contain at least [ItemNo]
> > and most likely all
> > >the other fields.
> > >
> > >If creating a catalog is not the correct path, please
> > advise of other
> > >options.
> > >
> > >thanks!
> > >
> > >
> > >
> > >.
> > >
>
>