vb.org Archive - Is there anything under the Maint. tab that should be run often?

vb.org Archive (https://vborg.vbsupport.ru/index.php)

- vB3 General Discussions (https://vborg.vbsupport.ru/forumdisplay.php?f=111)

- - Is there anything under the Maint. tab that should be run often? (https://vborg.vbsupport.ru/showthread.php?t=190099)

TMH63

09-05-2008 12:06 PM

Is there anything under the Maint. tab that should be run often?

Do any of you suggest to perform any tasks in Maintenance on a regular basis?

I'm not running into any issues(that I know of), but just curious if there are things that need to be done but I'm just not doing them.

Thanks!

Opserty

09-05-2008 12:08 PM

Nope.

TMH63

09-05-2008 12:09 PM

Quote:

Originally Posted by Opserty (Post 1615100)

Nope.

Wow...that was fast. ha, ha

Thank you for the response.

Lynne

09-05-2008 03:53 PM

The only thing I run occassionally (once a month?) is the repair/optimize on my tables. I'm sure some would say even that is not necessary.

Opserty

09-05-2008 04:06 PM

Quote:

If you are receiving strange errors or feel that your forum has recently become slightly more sluggish, go to Maintenance > Repair / Optimize Tables.

Maintenance / Repair / Optimize Tables

Marco van Herwaarden

09-06-2008 08:45 AM

Actually that is not needed and could even in worse case scenario cause a database crash.

Lynne

09-06-2008 03:26 PM

Quote:

Originally Posted by Marco van Herwaarden (Post 1615719)

Actually that is not needed and could even in worse case scenario cause a database crash.

Really? I had tried googling this once and got nowhere (or at least found no pages that explained it in terms that made sense to me). So, what you are saying is don't ever run repair/optimize unless there is a problem?

Marco van Herwaarden

09-07-2008 09:11 AM

Yes, only use it in case of a table corruption.

Repair/Optimise is rewriting most of the table information. Like with any writes, corruption can occur (worst case). A bad sector on the disk, a process crash, etc.. might leave your table totally corrupted if it happens in the middle of a repair/optimisation.

If you really want to optimise your tables, the best way to do so would be to create a backup of your database, delete and recreate the database and restore again.

a normal "optimise" does nothing more then merging consequtive emtpy blocks.

All times are GMT. The time now is 11:42 AM.

X vBulletin 3.8.12 by vBS Debug Information
Page Generation 0.01062 seconds Memory Usage 1,724KB Queries Executed 10 (?)
More Information
Template Usage: (1)ad_footer_end (1)ad_footer_start (1)ad_header_end (1)ad_header_logo (1)ad_navbar_below (3)bbcode_quote_printable (1)footer (1)gobutton (1)header (1)headinclude (6)option (1)post_thanks_navbar_search (1)printthread (8)printthreadbit (1)spacer_close (1)spacer_open Phrase Groups Available: global postbit showthread	Included Files: ./printthread.php ./global.php ./includes/init.php ./includes/class_core.php ./includes/config.php ./includes/functions.php ./includes/class_hook.php ./includes/modsystem_functions.php ./includes/class_bbcode_alt.php ./includes/class_bbcode.php ./includes/functions_bigthree.php Hooks Called: init_startup init_startup_session_setup_start init_startup_session_setup_complete cache_permissions fetch_threadinfo_query fetch_threadinfo fetch_foruminfo style_fetch cache_templates global_start parse_templates global_setup_complete printthread_start bbcode_fetch_tags bbcode_create bbcode_parse_start bbcode_parse_complete_precache bbcode_parse_complete printthread_post printthread_complete
Messages: