Server Log File Size...

[Kevin McC]

Guru's...

Our IT Sys Admin guy has just informed me that our Project Server Log File
has gone from a norm of around 2GB....to a rather huge greater than 10GB
OVERNIGHT...

I have no idea why this should happen, as there was only normal (in fact
probably less than normal for yesterday) activity.

I realise that I've not given much information here, but does anyone know
why this maight happen...or has anyone had a similar log-file explosion...???

As always, any feedback is much appreciated.

Thanks,

 

[Kevin McC]

More info on this issue...

The LARGE file in question is the 'ldf' file (now approaching 13GB!!!) - the
SQL transaction file...
The 'mdf' file is around 1GB in size...

Again, any help on this is appreciated...

Many Thanks..

 

[kwwatson]

Two replys from project pro server blog.

Periodically, you need to shrink the log file size. That should be part
of
regular system maintenance. You can use SQL Enterprise Manager or run
SQL
statement (BACKUP LOG.... WITH NO_LOG) from Query Analyzer to shrink
the
log file size.




Your huge problem started when you fired up the application without
regard
to backing up and maintaining the SQL database. You need to backup your

database and truncate the log file. Then you need to setup a
maintenance
plan so this happens automatically, or consider moving to a simple
recovery
method.

 

[Kevin McC]

Thanks to (e-mail address removed) for posting a reply...

I passed it on to my SysAdmin guy, who replies....

Response to news forum from an embarrassed sysadmin:

"My initial response when looking at the large increase in log file size was
to assume that project itself was doing a lot of work in the background. It
was only after an full backup followed by an incremental (with no difference
in transaction log size that I realized where the problem lay"

When recreating the incremental job last week for sql, i'd forgotten to
change the sql backup type from Full to Log and the sql logs are truncated
(For the curious we use BackupExec 10). There is now 15G 'free space' in the
database file according to sql, and the scheduled shrink process should bring
that down over a few days."
+++++++++++++++++++++++++++++++++

Once again, thanks for your response to this query...