Hi,

We're having a bit of trouble using the newest version of DNN, everything is installed and works almost perfectly, however every day around the same time our SQL server just stops and causes DNN to show an error message.  It's easily corrected by just starting up the server again, but naturally we'd rather find out what the problem is.  DNN is the only thing that makes use of the SQL server at the moment.  Could this be caused by something DNN is using, or is it likely to be something else?

Any help would be very much appreciated,

Cheers,

Steve

No worries,

Our CPU is running at pretty much 100% as well.  Our server stops round about the same time every day that the Google spider crawls the site, it's a possibility that the hits from Google (on top of another problem) might be causing the crashes. 

I'm amazed there's not more discussion or information on this. I just ran into this with one of my clients. His sites were almost totally non-responsive and the CPU was completely pegged even though there was very little traffic. We wrote a SQL script to Truncate the ScheduleHistory table for each DNN Database and now things are flying and the CPU has yet to go above 40% usage and rarely goes above 10%.

I did find one ticket in the Core, http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=5639 but that was only for 4.5.1 and we were seeing this problem in 4.3.7.

Looking at the public bugs in Gemini, http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=2272, it appears they did update the GetSchedule StoredProcedure in version 4.4.1 (which was the big performance tweaking release). So perhaps the best fix is for us to upgrade to 4.4.1 or newer.