Hi,
No I did not got this resolved.
I tell you why I do this truncation, shrinking.
In the past, when I did nothing< the database was growing and growing in size.
Then when, I wanted to empty the site log, I got an error mentioned that the log file was to big to complete the job.
So I had to find another way to empty the log file.
On the forum I discovered above mentioned script to empty the log file.
This script worked fine.
The database was shrinking from 50 to 25 Mb.
Then I saw on a site a free DNN module to do this job.
I installed this module.
I though everything was ok now.
However, after a couple of weeks I checked the database and event log again and it was big in size.
I tried to manually empty the log file and got again the error that the log file was to big to complete the job.
I used the old script to do the job again.
However, I upgraded the SQL from 2000 to 2008.
Now I got again an error that this script was not valid anymore.
What shall I do now?
using this?
ALTER DATABASE <%YOURDB> SET RECOVERY FULL
or this?
ALTER DATABASE c1664_dnn SET RECOVERY SIMPLE
TRUNCATE TABLE {databaseOwner}{objectQualifier}EventLog
TRUNCATE TABLE {databaseOwner}{objectQualifier}SiteLog
TRUNCATE TABLE {databaseOwner}{objectQualifier}schedulehistory
or this?
ALTER DATABASE <%YOURDB> SET RECOVERY SIMPLE
ALTER DATABASE <%YOURDB> SET RECOVERY FULL
Thanks for responding.
With regards, Ton Hermes