Re: SQL 2005 + MOSS 2007 + Size config LOG

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

If you leave the database in full recovery model, then you will need to modify your maintenance plans to include another job that runs every hour (or more often) that backs up the transaction log. Once you have that job setup and running, you can run the shrinkfile and shrink the file. The file will grow again to handle the number of transactions you have between each transaction log backup.

Having just setup a sharepoint database system, I can agree with the previous post and say that you don't need full recovery model. Change the recovery model to simple - shrink the file to 10MB and don't worry about it.

BTW - I would eliminate the Backup Exec job that backs up the database. Use the native SQL Server backup to back the database up to a file and then use Backup Exec to backup those files.

Jeff

"Juergen N." <jn@xxxxxxxxxxxx> wrote in message news:eQ$8LTIBKHA.4168@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

thanks for the fast answer. Yes, I'm talking about the SharePoint_Config database (SharePoint_Config_log.LDF)
To reduce physical size can I use for example thi command or what are the recommended settings?

USE SharePoint_Config
GO
DBCC SHRINKFILE(SharePoint_Config_log, 1)
BACKUP LOG SharePoint_Config WITH TRUNCATE_ONLY
DBCC SHRINKFILE(SharePoint_Config_log, 1)


best regards,

Juergen N.


"Uri Dimant" <urid@xxxxxxxxxxx> schrieb im Newsbeitrag news:Omu9PMIBKHA.3556@xxxxxxxxxxxxxxxxxxxxxxx
Hi
Are you talking about SharePoint_Config database. Set it up to SIMPLE recoveru mode. Also in order to reduce physical size of the file use
DBCC SHRINKFILE command






"Juergen N." <jn@xxxxxxxxxxxx> wrote in message news:erEmtJIBKHA.4168@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

we use SharePoint 2007 SP1 with SQL 2005 SP3. The databases at the moment are about 850MB,
but the config Log file is about 41GB !
For backup we use a scheduled task (Server Management Studio, full backup) and additionally Backup Exec 12.5
- when I select the config database - shrink file i see only 0,64MB free space of 41GB!?
- the recovery model is set tu Full

I have less experience with SQL so I'm not sure what's the best way to shrink or reduce the size
of the logfile.

any suggestions would be graitly appreciated,

best regards,

Jürgen N.





.

Relevant Pages

  • What is the best practice to create Maintenance Plans
    ... There is not a definitive answer to the question of which backup is better. ... the database can be recovered to the point ... Full Recovery or Bulk-Logged Recovery model. ... Transaction Log backup for master database is not allowed. ...
    (microsoft.public.sqlserver.security)
  • Re: How to PURGE a transaction log?
    ... This doesn't shrink the actual file size. ... Make sure you understand backup and restore architecture for 6.5 *really* ... make sure you understand the database architecture regarding database ... doing dummy transactions and DUMP TRANSACTION until the log have moved ...
    (microsoft.public.sqlserver.setup)
  • Re: Log file is increeasing too much
    ... If you are using the FULL recovery model, you would need to backup the log ... Need smaller SQL2K backup files? ... > i have a database and a proccess which delete everything from database and ... > backup log mydatabase with truncate_only ...
    (microsoft.public.sqlserver.server)
  • Re: Sharepoint and SQL Recovery Model
    ... SQL Server 2000 uses recovery models to help you plan backups. ... You can use either Simply or Full Recovery Model based on your need. ... be recovered to the point of the last backup. ... The SharePoint Portal Server 2003 configuration database. ...
    (microsoft.public.sharepoint.portalserver)
  • Re: How can I assign the result of dateadd to a variable ?
    ... It then stays in the database until 4 days later when it ... I now check the "Check Database Integrity" option with "Include Indexes", ... I have now changed the recovery model to "Simple" (In Enterprise Manager, ... > modifications since your last backup? ...
    (microsoft.public.sqlserver.programming)