Truncating the SQL transaction log file
(Doc ID 446902.1)
Last updated on DECEMBER 28, 2022
Applies to:Oracle WebCenter Content - Version 7.0 and later
Information in this document applies to any platform.
Product: Content Server
We are using MS SQL Server 2000 as our backend database for our Stellent installation. When I look at the properties of that database, the data file is 238 MB and transaction log file is 33+ GB. I would like to reduce the size of the transaction log file by using a T-SQL statement to truncate it, but I do not know what the consequences would be to your application. Does
Stellent reference the transaction log file for the history of the documents that are checked into it? And if it does not, would it be safe to truncate the transaction log?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document