Re: Setting Up Full Text Search For WSS

When you installed WSS did you install it with the default installation?

In such a case you would have in addition to your SQL Server on D: a copy of
WMSDE on C:

The copy of WMSDE would be in that case the location for the WSS databases
and because WMSDE does not support Full-Text search Full-Text search would
(probably) be grayed out.

Otherwise you would not usually have databases on both C: and D:

However as this is a SBS 2003 installation things might be different there,
so if this answer doesn't help you please post to the SBS newsgroup at

microsoft.windows.server.sbs

as this newsgroup only deals with standard WSS and things in other
implementations that also may arise in standard WSS. Having databases on two
drives does not occur in standard WSS.

Mike Walsh, Helsinki, Finland
WSS FAQ at http://wss.collutions.com
Please reply to the newsgroup

"Jeff Teel" <jdteel@xxxxxxxxxxxx> wrote in message
news:OyaHU1yiFHA.576@xxxxxxxxxxxxxxxxxxxxxxx
>I have Windows Small Business Server 2003 SP1 and am using WSS with SQL
>2000 SP4 for data storage of the SharePoint sites. I have enabled the
>Search component for my SharePoint webs in Central Administration and the
>Search box now appears at the top right of the pages. When I do a search
>for documents that are in my web nothing is returned. I have Microsoft
>Excel and Word documents in the SharePoint web. I noticed that when looking
>in SQL Enterprise Manager that my SharePoint instance did not have
>Full-Text Search installed. My other SQL instance does have and I see the
>Full-Text Search Icon under Support Services. I installed the search
>component on my SharePoint instance but there is still no Full-Text Search
>icon under Support Services. On my SharePoint instance I do see Full-Text
>Indexing under the Tools menu but it is grayed out. Before installing the
>search component on the SharePoint instance it Full-Text Indexing was not
>under the Tools menu.
>
> My question is regarding where the database for the SharePoint instance
> resides. The instance where I see Full-Text Indexing under the Tools Menu
> of SQL Enterprise Manager the database is on the D:/ drive and the
> SharePoint instance has the database stored on the C:/ drive. Should both
> databases be on the same drive? Should I move the SharePoint database to
> the D:/ to make the Search engine work?
>
> Thanks
> Jeff
>


.

Relevant Pages

  • Re: SQL cluster search problems - this may help
    ... Given that the problem was caused by DLL differences in an SQL installation, ... standalone WSS users. ... Although I don't have a standalone installation of WSS, ...
    (microsoft.public.sharepoint.portalserver)
  • Re: SQL cluster search problems - this may help
    ... Given that the problem was caused by DLL differences in an SQL installation, ... standalone WSS users. ... Although I don't have a standalone installation of WSS, ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Follow-up Question
    ... Considering removing WSS and do a clean installsince SQL ... >I've done this in site upgrade from WMSDE to SQL Server ... >>If this means that you ran a default installation of WSS ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Follow-up Question
    ... Considering removing WSS and do a clean installsince SQL ... >I've done this in site upgrade from WMSDE to SQL Server ... >>If this means that you ran a default installation of WSS ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Why use WSS and not MSSX?
    ... SQL Server is usually enough and is something to move to when a single server WSS 3.0 installation is having load problems. ... Look at the sticky post I wrote in the General and Setup/Admin forums for information on which forum is suitable for what. ... The major difference I can suggest is that MSSX comes with a database ...
    (microsoft.public.sharepoint.windowsservices)