Events Log Maintenance (TUTORIAL)
For me, it wasn't until using Dotnetnuke version 4.5.0 and above that I found my website database was growing each day by an enormous amount. Probably 40MB per day. It doesn't take very long to realize you are not going to have much hosting space left if this keeps going on unchecked. Therefore, I needed to look more into why the database was growing so large, so quickly.
To see how large your eventlog is, log into your dotnetnuke website as host, on the menu go to SQL, and run the command "exec sp_spaceused eventlog" as shown below (This is from within Dotnetnuke). This will run a stored procedure that will display the size of your eventlog. In this case below, I have run the command after I fixed my eventlog size issue and this slightly over 1MB size is much more managable.
Once the event log was found to be the culprit, I needed to find a way of quickly deleting a 500MB eventlog from my database. Running a stored procedure for SQL successfully reduced the size of my database. This simple command was "DELETE FROM EventLog" and was run from within a SQL command query screen like shown below. (This was from within my hosting server's sqladmin interface)
Now to keep the log files from growing too large, you will need to tell Dotnetnuke how many records to keep, rather than the default of store "all" records. The default values I found for version 4.5.0 are shown below.
Okay, so what I want to do here is to enable the purge event log service and configure it to run. Editing the currently disabled record and enabling it looks as shown below.
Now that I have ticked the option as shown above for enabling the service, and clicking the update link to save my new settings, I an see the new list below.
To check that this have been started, you can click on the History links shown on the right of each service as shown below.
This was all I needed to do to ensure my event log files were not going to use up all of my database space.