CornerPixel Blog RSS 2.0

# Monday, November 02, 2009

Today I was doing a database backup for a DotNetNuke website.  When I did the backup, I was amazed at how big the database was.

I tried to shrink it, and it didn’t work.

The next thing I did was Googled it, and found a little help in pointing me to what the issue was.  A couple posts in the DotNetNuke forums had commented on big events logs, so I checked mine out.

581MB!!!

Okay now how to clear this?  I couldn’t even view them via the website when logged in as “host”.

I cleared them by doing the following steps.

  1. Log into your website as a "host user"
  2. Go to Host > SQL
  3. Run the script below

    Truncate table eventlog
  4. Logged into my SQL server and Shrunk the database
  5. All my issues were solved!!

This seems like an easy no brainer, but I hope it helps people out there with there DNN databases.

Oh and one other helpful hint:  Set your db’s “Recovery Model” to be simple in the options, if you backup your database on a regular basis.  This will keep your db from getting too big also.

Monday, November 02, 2009 2:43:45 AM (Pacific Standard Time, UTC-08:00)

#       Comments [0] - Trackback

CMS | DotNetNuke | SQL

Comments are closed.

Archive

<July 2010>
SunMonTueWedThuFriSat
27282930123
45678910
11121314151617
18192021222324
25262728293031
1234567

Email Subscription

Sign up to get the CornerPixel Blog delivered to your email.

About the Author

Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

Sign In

Statistics

Total Posts: 52
This Year: 3
This Month: 0
This Week: 0
Comments: 28