Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...SQL server constantly having CPU peggedSQL server constantly having CPU pegged
Previous
 
Next
New Post
2/14/2006 2:40 PM
 
swillhite (mrswoop) wrote

 

Maybe you should consider the Benefactor program?

Sounds like a good deal to me.  I will sign up at least for the Silver Level shortly.  I'd sign up now but I'm dishing out a ton and taking in nothing.  Give me a week or so and you'll see an icon next to my name.  Does the private forum imply that more people will be able to help with my oddities?

I see it like this...  DotNetNuke has made an investment in me.  I'm just a normal guy, working a normal job.  I'm not wealthly... nowhere near it.  I stumbled onto DNN one day and had a good idea. I've taken a considerable amount from the DotNetNuke project and community in hopes that my own project will be successful.  Once I have even a hint of success, I plan on repaying the DotNetNuke project and community back greatly.

I would love to sign up for the Benefactor program.  Unfortunately, I don't have the cash lying around at this moment, however, hopefully my paypal account will have a few hundred deposited soon.  Then I'll have a happy icon by my name.  Promise!

Honestly, Tim, if makes me a little nervous ( for your 2000 portal admins ) to hear you ask the kinds of questions that I am seeing in this ( and other ) threads.  Forgive me, but I would be remiss for not mentioning it.

I'm learning just like the rest of them :)

I have a copy... I must have missed a lot if good information.  I'll check it out some more :)

It's highly likely that the single most frequently occuring item in your EventLog is an error for purging that log ( trimming its history by date )... which is probably failing every few minutes.

I have set in the Host->Settings to have the EventLog buffer 0 and days 0, yet there still is a ton of things written to the EventLog.  I can't quite seem to purge it, either.  Could you tell me the best way to purge it, as well as how to flat out make portals not use the Event Log at all?

 
New Post
2/14/2006 4:23 PM
 

I forgot to say this - Thank you a LOT for your replies Scott.

I just checked my EventLog and it is pretty much just full of people logging in, adding modules, etc.  It is about 3 million records large right now.   It looks like I have 0 EventLog days and 0 buffer set in my Host->Site Settings, but I take it that does not affect all portals, just the 1 I logged into as Host.  Oh well, I can update all the portals manually.

So the trick now... the best way to purge my EventLog.  Is it okay if I simply just drop all my records manually?  Or perhaps there is a better way?  The Scheduled SQL command fails everytime it runs :p

 
New Post
2/14/2006 11:52 PM
 

Tim,

I just seen your other message and found your site (Sites).  VERY cool idea (I play WoW alot.)  I wish I would have had it.  :)

Looks like you have bumped in to one of those places where Oracle beats SQL Server.  The eventlog purge is most likely failing because the transaction log fills up all the availble DB space. Your best bet to get rid of the data in the eventlog is to truncate with out logging.  The script that DNN uses deletes one record after another and depending on how you designed the DB  the transaction log could fill up after only 100 records.

To delete 3 million + records (Never to be seen again) do TRUNCATE TABLE EventLog.

If you can, schedule regular database backups also.  In your case maybe every couple hours.  :)  This also keeps the transaction logs from filling the database as the only time they are truncated is during a backup and only the transactions you don't need to recreate your database are deleted.

For a site this big there are probably a few more optimzations to the DB you might want to consider also.

You also might run into this problem with the SiteLog table.  I did twice, once getting slashdoted and the other posting a link to those Danish cartoons.  I've got a little tiny database and it couldn't handle it.


Paul Davis
 
New Post
2/14/2006 11:57 PM
 
I forgot to mention you should probably keep logging active just limit the number to something like the last 100 or so.  By default  it's set to keep all of them. 

Paul Davis
 
New Post
2/15/2006 2:18 AM
 

Heya there!!!  Thanks for the kind words :) 

When you say the transaction log fills up all the available DB space.. do you mean actual space on my server?  I have about 4 TB free of drive space atm heh.  But otherwise, I am backing up my database now and I am going to truncate as you suggested!

Site Log as well, hmm!  Not a bad idea.  I am going to do the EventLog first and go from there.

So do you have any idea what could possible be keeping my SQL server constantly between 50-75% CPU? It never, ever, drops below 50%, not a single time.  I just can't figure it out.  Even if I'm only serving a few pages a second in my slow times, it never drops below 50%. 

Thx tonnnage!

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...SQL server constantly having CPU peggedSQL server constantly having CPU pegged


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out