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 2005 ProblemSQL Server 2005 Problem
Previous
 
Next
New Post
6/17/2007 7:36 AM
 

there might be various reasons for a CPU of 100 percent - you need to analyse, which application causes the high CPU usage, e.g. using process explorer from microsoft. Next you ca try to narrow down teh issue in this application, e.g. the SQL script that causes the load, if SQL server is affected.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/18/2007 10:01 AM
 

Another item to check is to see when and how often the "Search Scheduler" task is running that is one that can take a large amount of CPU time on larger sites.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
6/18/2007 1:41 PM
 

Also, is this SQL Server 2005 or SQL Server 2005 Express?  Express has a few limitations that may be causing some of this.  Like the buffer pool limts.

Jeff

 
New Post
6/18/2007 1:53 PM
 

Seems I need to be more clear...

My problem was fixed, temporarily at least, by clearing the ScheduleHistory table. The GetSchedule StoredProcedure as it is written in 4.3.7 combined with thousands of records in the ScheduleHistory table was the problem.

I'm hopeful that the problem will not reoccur as hopefully the scheduled PurgeScheduleHistory event will be run on a regular basis as it was originally setup. As long as this is functioning the way it was written, this problem shouldn't occur for most people. But if something occurs on a particular site that keeps PurgeScheduleHistory from getting scheduled, the site will continually degrade.

The GetSchedule SP was re-written for 4.4.0. Hopefully that solves this problem for all newer installations though apparently, further improvements can be made for the SP as was proposed in the first ticket I referenced.


David O'Leary
Efficion Consulting
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...SQL Server 2005 ProblemSQL Server 2005 Problem


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