Transaction log is getting bigger and bigger

H

Hans Wurst

....due to a SQL process called MSP_WEB_SP_QRY_ViewTaskSplits_DeleteViewTable0;1

Our admin kills that process to get the space of the transactionlog back (25
GB)

Has anyone of you an idea what that job does or how we can solve the problem?

Oldest active transaction:
SPID (server process ID) : 58
UID (user ID) : 5
Name : user_transaction
LSN : (116132:258229:1)
Start time : Dec 1 2006 3:57:34:340PM
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
 
M

Marc Schoeni

Hans Wurst,

I would recommend you to set-up a scheduled job on your SQL Server to
truncate the Project Server DB log e.g. every week. This will dramatically
cut the size of the log file.

backup log <DBName> with truncate_only
dbcc shrinkfile(<LogFileName>, 1)
dbcc shrinkdatabase(<DBName>, 0, TRUNCATEONLY)

I would recommend you to set-up the same scheduled job for your WSS Content
database if you're using SharePoint.

Hope this helps...

Marc S.
MCP for EPM
www.diventis.ch
www.msepm.blogspot.com
 
Top