Hi Bruce,
I have a suggestion for you to try, but before anything, BACKUP! :)
1 - First identify the table that has grown crazy over this period. My guess is that you have all event logs been logged. Try to run the following script under Host/SQL:
SELECT
Coalesce(8 * Sum(CASE WHEN si.indid IN (255) THEN si.reserved END), 0) AS blob_kb
, 8 * Sum(CASE WHEN si.indid IN (0, 1) THEN si.reserved END) AS data_kb
, Coalesce(8 * Sum(CASE WHEN si.indid NOT IN (0, 1, 255) THEN si.reserved END), 0) AS index_kb
, so.name
FROM dbo.sysobjects AS so
JOIN dbo.sysindexes AS si
ON (si.id = so.id)
WHERE 'U' = so.type
GROUP BY so.name
ORDER BY 8 * Sum(CASE WHEN si.indid IN (0, 1) THEN si.reserved END) Desc
It should show at the very top which table has grown most.
My bet is that it was either EventLog or ScheduleHistory (or both)
IF it is one of those two, you can safely run the following to delete all records from them:
TRUNCATE TABLE EventLog
go
TRUNCATE TABLE ScheduleHistory
go
If it is another table that has grown, then you can post its name here so I can have a look.
2 - Now we need to clean up the big log file. To do that you can run this SQL statement:
dbcc shrinkfile([DB FILE NAME] ,1)
go
dbcc shrinkfile([LOG FILE NAME],1)
go
backup log [NAME] with truncate_only
go
You should find and replace [DB FILE NAME], [LOG FILE NAME] and [NAME] with the correct information you have gotten from the Dashboard regarding your database.
3 - That this script fails, try running the following one and then run them again:
Alter database [NAME] SET Recovery simple
4 - If the cause was the event log, now you should disable the event log from your site by going to Admin/Event Viewer. You should go to each event and disable them.
I hope this will be able to drop the big log file you have. This is the process I personally use whenever I come across this scenario.
Cheers,
Aderson