Re: SQL Database size excessively increasing after Site Collection Restore
- From: Dandare00uk <dan@xxxxxxxxxxxxxxxx>
- Date: Thu, 25 Oct 2007 08:44:53 -0700
On 25 Oct, 14:13, SmartbizAustralia <t...@xxxxxxxxxxxxxxx> wrote:
This is a common issue not limited to SharePoint databases!
Sounds like you are using the full logged method and your maintenance
plan isn't setup correctly!
Also make sure you have the right service pack if you have sp2 for sql
server as there were a few releases of this...
If you never backup the log file it grows out of proportion!
Get a SQL Server DBA who knows what he is doing!
Regards,
Tom Bizannes
Microsft SharePoint and Sql Server Specialist
Sydney, Australia
Would love to have a DBA here. This particular problem we believe is
something to do with how WSS3.0 restores. No normal SQL backups or
restores are performed all actions are performed by stsadm.
Even when we deleted the contents database via WSS admin the SQL DB
size remained.
Any further ideas?
.
- References:
- SQL Database size excessively increasing after Site Collection Restore
- From: Dandare00uk
- Re: SQL Database size excessively increasing after Site Collection Restore
- From: Wayne Atkinson
- Re: SQL Database size excessively increasing after Site Collection Restore
- From: Dandare00uk
- Re: SQL Database size excessively increasing after Site Collection Restore
- From: SmartbizAustralia
- SQL Database size excessively increasing after Site Collection Restore
- Prev by Date: Re: admin guide for 3.0
- Next by Date: How to FTP or Copy (using .bat or .vbs) files to a file director
- Previous by thread: Re: SQL Database size excessively increasing after Site Collection Restore
- Next by thread: Re: SQL Database size excessively increasing after Site Collection Restore
- Index(es):
Relevant Pages
|
|
