FT Searching in SQL Server Database

We've got a small Windows SharePoint Services site that stores content
in a remote SQL Server Database. Over the last couple of weeks I've
been trying to get the Search Service working to no avail - no results
are being returned when a search is being performed.
I've posted this to the Windows Sharepoint Group, but I suspect the
problem may be with the SQL Server installation. Here's a summary of
the setup/things checked... any pointers would be appreciated!
1. I'm running SQL Server 2000 with SP3
2. The Full Text component of SQL Server is installed
3. The Microsoft Search Service is running and logged in using local
system admin account
4. There are no errors reported in the Event Log
A clean install of WSS was performed and the FT Search and Indexing
option for the site under SharePoint is all configured correctly.
When I look at the WSS Installation Guide it talks about an empty
index being created called ix_<databasename> when WSS is installed. I
have very little experience of SQL Server, but I did check this using
Enterprise Manager and nothing exists under the Full Text Catalogs
node. Is it possible to recreat this manually?
Thanks.Steve,
Windows SharePoint Services or WSS as it's sometimes called, can use SQL
Server's Full-Text Search (FTS) components. However, you need to do a couple
of things when you migrate or upgrade from WMSDE (a special Windows 2003
version of MSDE) to SQL Server. Specifically, for your named instance
"SHAREPOINT", when you upgraded to SQL Server, under Server Components, did
you elect the Full-text Search check box?
Note, you can also post FTS related questions to the newsgroup:
microsoft.public.sqlserver.fulltext
Regards,
John
"Steve" <bennett_s_nospam@.yahoo.com> wrote in message
news:190ea2c6.0312031335.630fc2dc@.posting.google.com...
> We've got a small Windows SharePoint Services site that stores content
> in a remote SQL Server Database. Over the last couple of weeks I've
> been trying to get the Search Service working to no avail - no results
> are being returned when a search is being performed.
> I've posted this to the Windows Sharepoint Group, but I suspect the
> problem may be with the SQL Server installation. Here's a summary of
> the setup/things checked... any pointers would be appreciated!
> 1. I'm running SQL Server 2000 with SP3
> 2. The Full Text component of SQL Server is installed
> 3. The Microsoft Search Service is running and logged in using local
> system admin account
> 4. There are no errors reported in the Event Log
>
> A clean install of WSS was performed and the FT Search and Indexing
> option for the site under SharePoint is all configured correctly.
> When I look at the WSS Installation Guide it talks about an empty
> index being created called ix_<databasename> when WSS is installed. I
> have very little experience of SQL Server, but I did check this using
> Enterprise Manager and nothing exists under the Full Text Catalogs
> node. Is it possible to recreat this manually?
> Thanks.

FrontPage/SharePoint Designer Search and Replace Fills Transaction

When we run a search and replace across all pages in one our web site (104
pages), my transaction log on the SQL Server grows by about 200 MB of space!
This has caused major system headaches - the transaction log fills, causes
IIS to fail, causing my clients using FP / SP Designer not to be able to save
the files they have opened / edited.
That database is 400MB in size while the Transaction Log is now over 6GB.
and the minimum Log is now 6GB too. We can't keep having this log grow
exponential like this.
Also - In the event log, I see that there a couple of 'webparts' that are
failing on the global search and replace: WSS 2.0 Error: Failing in loading
assemble Customer.WebParts, Version=1.0.2.4.
We're running SQL Server 2000 SP4, on a Windows 2003 Server with WSS 2.0
using the latest versions of FrontPage and SharePoint Designer.
Thoughts?
After posting this, I started to search the WSS / Sharepoint forums (instead
of just SQL Server) and see that this is a common issue and found a variety
of ways to correct this.
Iza
"iZa" wrote:

> When we run a search and replace across all pages in one our web site (104
> pages), my transaction log on the SQL Server grows by about 200 MB of space!
> This has caused major system headaches - the transaction log fills, causes
> IIS to fail, causing my clients using FP / SP Designer not to be able to save
> the files they have opened / edited.
> That database is 400MB in size while the Transaction Log is now over 6GB.
> and the minimum Log is now 6GB too. We can't keep having this log grow
> exponential like this.
> Also - In the event log, I see that there a couple of 'webparts' that are
> failing on the global search and replace: WSS 2.0 Error: Failing in loading
> assemble Customer.WebParts, Version=1.0.2.4.
> We're running SQL Server 2000 SP4, on a Windows 2003 Server with WSS 2.0
> using the latest versions of FrontPage and SharePoint Designer.
> Thoughts?

FrontPage/SharePoint Designer Search and Replace Fills Transaction

When we run a search and replace across all pages in one our web site (104
pages), my transaction log on the SQL Server grows by about 200 MB of space!
This has caused major system headaches - the transaction log fills, causes
IIS to fail, causing my clients using FP / SP Designer not to be able to save
the files they have opened / edited.
That database is 400MB in size while the Transaction Log is now over 6GB.
and the minimum Log is now 6GB too. We can't keep having this log grow
exponential like this.
Also - In the event log, I see that there a couple of 'webparts' that are
failing on the global search and replace: WSS 2.0 Error: Failing in loading
assemble Customer.WebParts, Version=1.0.2.4.
We're running SQL Server 2000 SP4, on a Windows 2003 Server with WSS 2.0
using the latest versions of FrontPage and SharePoint Designer.
Thoughts?After posting this, I started to search the WSS / Sharepoint forums (instead
of just SQL Server) and see that this is a common issue and found a variety
of ways to correct this.
Iza
"iZa" wrote:
> When we run a search and replace across all pages in one our web site (104
> pages), my transaction log on the SQL Server grows by about 200 MB of space!
> This has caused major system headaches - the transaction log fills, causes
> IIS to fail, causing my clients using FP / SP Designer not to be able to save
> the files they have opened / edited.
> That database is 400MB in size while the Transaction Log is now over 6GB.
> and the minimum Log is now 6GB too. We can't keep having this log grow
> exponential like this.
> Also - In the event log, I see that there a couple of 'webparts' that are
> failing on the global search and replace: WSS 2.0 Error: Failing in loading
> assemble Customer.WebParts, Version=1.0.2.4.
> We're running SQL Server 2000 SP4, on a Windows 2003 Server with WSS 2.0
> using the latest versions of FrontPage and SharePoint Designer.
> Thoughts?sql

FrontPage/SharePoint Designer Search and Replace Fills Transaction

When we run a search and replace across all pages in one our web site (104
pages), my transaction log on the SQL Server grows by about 200 MB of space!
This has caused major system headaches - the transaction log fills, causes
IIS to fail, causing my clients using FP / SP Designer not to be able to sav
e
the files they have opened / edited.
That database is 400MB in size while the Transaction Log is now over 6GB.
and the minimum Log is now 6GB too. We can't keep having this log grow
exponential like this.
Also - In the event log, I see that there a couple of 'webparts' that are
failing on the global search and replace: WSS 2.0 Error: Failing in loading
assemble Customer.WebParts, Version=1.0.2.4.
We're running SQL Server 2000 SP4, on a Windows 2003 Server with WSS 2.0
using the latest versions of FrontPage and SharePoint Designer.
Thoughts?After posting this, I started to search the WSS / Sharepoint forums (instead
of just SQL Server) and see that this is a common issue and found a variety
of ways to correct this.
Iza
"iZa" wrote:

> When we run a search and replace across all pages in one our web site (104
> pages), my transaction log on the SQL Server grows by about 200 MB of spac
e!
> This has caused major system headaches - the transaction log fills, causes
> IIS to fail, causing my clients using FP / SP Designer not to be able to s
ave
> the files they have opened / edited.
> That database is 400MB in size while the Transaction Log is now over 6GB.
> and the minimum Log is now 6GB too. We can't keep having this log grow
> exponential like this.
> Also - In the event log, I see that there a couple of 'webparts' that are
> failing on the global search and replace: WSS 2.0 Error: Failing in loadin
g
> assemble Customer.WebParts, Version=1.0.2.4.
> We're running SQL Server 2000 SP4, on a Windows 2003 Server with WSS 2.0
> using the latest versions of FrontPage and SharePoint Designer.
> Thoughts?