[TheLastSuperman]

Well one thing is for sure, routine maintenance can require a restart but a table crashing usually stems from something else, we need to find out why it crashed and ensure it doesn't happen again. I've pm'd you back but I want this thread to stay on topic; Flibnipktz asked for advice so lets give him solid advice no matter what is found to be the culprit... along the way some advice can always be given then in the end reviewed to make a well informed decision . Some advice may not even apply to this situation but others who find this thread after having similar db errors (if they search and somehting in your post comes up etc) might try some advice given and it work for them the point being sometimes not all advice is good for you but for others it might be... take that with a grain of salt because it does not apply to every situation.

I say keep most of it in PM because to me... how I feel about this is even if I'm not paid for this to me it feels like a paid request being discussed in public which I know its not - this is just me being nice with only a little effort involved yet I'd rather keep some stuff in PM's and have valued members contribute and give good solid advice instead of seemingly derailing your thread! So We'll keep most of this to PM's and if something comes up that explains it and I can elaborate on that in a "tutorial" or "if this ever happens to you, this might be the cause" type of way in this thread then I certainly will .

Edit: I deleted some older pm's my inbox was full, fixed now.