First... you need to know I'm an IT guy,  not a web-app or database guru/admin.  Read this as; I'm a complete dolt on both subjects. Worse yet, I have lost the guy who setup and configured DNN through "down-sizing".  Keeping DNN and SQL running has now been dumped in my lap.   That being said, I have a SQL server (version 2000) with the DNN database on it.  The database for DNN is about 56 megabytes but the darn SQL log file for DNN is 24 Gigabytes and rising.  This file grows at strang monthly intervals by about a Gig and a half.  It is now running the risk of filling the database partition on the server so I know I need to take some action, but what action?  I've done enough reading on SQL server that I believe I can "gut" the log file by seting up a "simple" backup plan (the setup guy never configured a backup plan for DNN), thus truncating the log file.  But... being a DNN dolt, I don't want to get myself into an unrecoverable corner by doing so.  Any advise would be appreciated.

biames

You can run sql script :

declare @DB as varchar(128)
set @DB='YourDNNDatabaseName'
print 'BACKUP LOG '+@DB+' WITH TRUNCATE_ONLY ...'
BACKUP LOG @DB WITH TRUNCATE_ONLY

print 'DBCC shrinkdatabase ('+@DB+',0,TRUNCATEONLY) ...'
DBCC shrinkdatabase (@DB,0,TRUNCATEONLY)
go


Set variable @DB with your DNN Database Name.