Lynn,

If you can convince your hosting provider to re-attach the database for you, and have them take your site offline you can perform cleaning via the database.

I am not sure of the specifics within the link that clay provided as when I follow it, my IE window crashes and since I am at work I am not going to try that again.

I would start by removing the old entries from your SiteLog and EventLog tables.  Also, look at the recent entries in the EventLog and see if they provide any information for you.

I would also look at the product in your store modules database tables that you mentioned was "problematic" and potentially remove it as well.

Your hosting provider should be willing to reattach the database as long as your DNN site is offline and not able to access the DB.  if you have not done so already you also might want to put an app_offline.htm file out for your users, this will allow you to give them an under construction message!

---

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


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

Hi

I have sent my hosting provider a request "ticket "to re-attach or send me the database.  I am waiting for a reply.

This is so scary.

---

www.seemalta.net

Hi Carlos,

It definitely was DNN in my case, and it has or at least had something to do with the events log and the scheduler logs being "large"  I agree it shouldn't have had any impact at all, but when those two tables were purged in the DB, the site began to literally "fly" using 4.4.1. 

My site was pegging out the CPU at almost 100% for up to 30 to 40 seconds per page called.  We didn't do a thing, other than purge the two offending tables,   Then we set a scheduled DB "task" in SQL to purge both tables periodicly ( I think it was about 20 days or so ) and I haven't had a single issue since.

Pages now load on first call in about 3 seconds from "hit" to "display" on my local screen from the remote site.  With these two changes made, 4.4.1 literally "screams."  

So, Lynn, there is hope and I am sure your host will give you the DB so you can purge it locally then FTP it back to them for re-attachment.  If you explain the problem to them, asking them to set  a "task" in SQL to purge the two tables once every couple of weeks or so, you should be fine.

Clay