Forum


HomeHomePremiumPremiumAdministrationAdministrationVideo: Keeping Database Tip TopVideo: Keeping Database Tip Top
Previous
 
Next
New Post
12/5/2013 5:20 AM
 
I recently experienced the issue that Aderson describes in video 2. My Database had “runaway” to 500MB. It turned out the scheduled tasks to Purge certain Tables had failed, namely SchedduleHistoryLog. It seems it runs a DELETE command which if it times out fails. Once it fails it never recovers.

My solution was to DELETE the whole file through SQL Server Management Studio and run a Script to reCREATE the Table.
This new procedure that Aderson has implemented should negate that ever happening in the future

In the video Aderson asks about other Tables to clean. The only other “large” table I have noticed is SearchItemWordPosition not sure what this does, so it might be an option for cleaning
 

 
New Post
12/5/2013 5:47 AM
 

Great point Dave about the SearchItemWordPosition.

That table is related to the default DNN search box. If your site doesn't use the DNN search then you can get rid of the content from that table and from a few others too this way:

TRUNCATE TABLE {objectQualifier}SearchItemWordPosition
TRUNCATE TABLE {objectQualifier}SearchItemWord
TRUNCATE TABLE {objectQualifier}SearchWord
TRUNCATE TABLE {objectQualifier}SearchItem

But if your site does use search, you should not do that as you just created more work for the search index procedure the next time it runs as it will have to recreate the search index again.

Also, if you don't use the search at all on your site, you should not only clean up these tables above, but you should actually DISABLE the search scheduler from running all together on the site. You can do that by going to Host/Schedule and disable "Search Engine Scheduler"

Thanks,

Aderson


 
Previous
 
Next
HomeHomePremiumPremiumAdministrationAdministrationVideo: Keeping Database Tip TopVideo: Keeping Database Tip Top



Try FREE
30 days money back guaranteed