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?

Free Pages is low

The Free Pages on our SQL server is consistently at 84 which I've read is
low. Any suggestions on how to improve this number?This is related to the memory allocated to SQL Server. If only SQL Server is
running in that machine, try to increase the "min server memory" occupied by
SQL Server.
for this, use sp_configure.. the syntax, you can check from BOL.
The other ways of increasing memory is by reducing the prcedure cache.
For more info, check this link
http://www.windowsitlibrary.com/Content/77/15/3.html
hope this helps
"Shane C" wrote:

> The Free Pages on our SQL server is consistently at 84 which I've read is
> low. Any suggestions on how to improve this number?