Website Upgrade Incoming - we're working on a new look (and speed!) standby while we deliver the project

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Recent upgrade to Primavera 6.7 SP1 – huge SQL transact

1 reply [Last post]
Stuart Fairweather
User offline. Last seen 14 years 40 weeks ago. Offline
Joined: 30 Mar 2010
Posts: 6
Groups: None
We’ve recently upgraded from Primavera 5.0 SP7 to 6.7 SP1 and we’re having major issues with the database transaction log (we’re using SQL Server 2005 running in 2000 compatibility mode). If we truncate the log it remains small for a few hours then starts to grow and within the space of a day it fills the server hard drive – 13GB in our case. Has anyone had similar problems? We didn’t have this problem when we were on P5 and no hardware or DB configurations have changed. The SYMON job appears to be running every minute as it should and we’ve scheduled DAMON to run daily (default 1 week).

Cheers

Replies

Rodel Marasigan
User offline. Last seen 25 weeks 4 days ago. Offline
Joined: 25 Oct 2006
Posts: 1699
Stuart,
P5 has a compact database function which is removed in P6.x to P6v7.
This was the function of SYMON and DAMON.
SYMON (System Monitor), responsible for running procedures that take less than a few seconds to complete. (default every minute)
DAMON (Data Monitor), responsible for running procedures that take longer than a few seconds to complete. (default weekly)

For log files I’m not too sure because I haven’t experience that yet but I’m sure it nothing to do with those system and data monitor that you mentioned.