There are at least three log tables in the database to which DNN may entries, thus growing the size of the database.

• EventLog table - this primary log records events including application starts/ends, user creation, user logins, module installs/upgrades, application errors, etc. It can grow quite rapidly in size, especially if there are frequent logins or repeated application errors being logged. To check this log file, log in as the host user and click on Admin-->Event Viewer. As host you can clear all or selected events and specify what type of events get logged.
• SiteLog table - this log (which is turned off by default) records user activity. The number of days of activity that are retained in the log can be set by the host user by clicking on Admin-->Site Settings-->Advanced Settings-->Host Settings. A scheduled task is supposed to automatically purge older activity entries but if that scheduled task has been disabled or is not working or the site is very active and the days the logged activity is retained is set to a high number, the SiteLog table can grow very rapidly. You can examine the site log by clicking on Admin-->Site Log.
• ScheduleHistory table - this log records the occurance or failure of scheduled events (such as that to purge the SiteLog table). A scheduled task is supposed to automatically purge older schedule history items. When logged in as host user, you may examine the schedule history and make changes to scheduled events (be very careful what you change!!) by clicking on Host-->Schedule.

Other modules and features also record their activity when enabled - user's on-line, link click tracking, etc. but the three tables mentioned above are the primary logging table.

Finally, the SQL server will maintain outside of DNN its own database log. This can also grow quite large for an active site. If the site is located on shared hosting, your hosting control panel or SQL maintenance tools should provide a way to backup the database and truncate the log file either manually or on a schedule. If you have access to the database via SQL Server Management Studio, etc. you can do your own backup and trunction of the database log file.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner