ok - it turns out that some database files were corrupted or deleted. Support - after obviously messing around with MySQL on the windows server for a good while now - and this kind of activity can indeed have this result, as can moving files to new servers etc. had the audacity to suggest that it might have been a password hack on my
website hosting or even bad scripting!!!! Unbelievable. I have been patient - I understand the problems that can be faced with MySQL on a windows system and have endeavoured to provide as much info about problems as I can, but when three MySQL
website hostings go down on three separate
website hostings simultaneously with identical errors (one of which a wordpress blog - so hopefully no bad scripting there) while technicians are working on the MySQL system, how can the blame possibly be directed towards me?? Furthermore, during yesterday the MySQL server was restarted and after which, my
website hostings rendered fine - for about 2 minutes - but in that time all data was present and visible before developing the original problem once more. Support seemed uninterested in this.
I have restored my tables via phpMyAdmin (luckily I keep backups) but am concerned at the dismissive tone from the support department - never an apology, always an accusation toward the customer.
Why could they not have just apologised for the inconvenience and explained that they have been working on the system and unfortunately some of my database files were corrupted or deleted. I would have accepted that in the hope that that work would ultimately lead to a stable system.
Perhaps yesterday was a bad day for your support department - several hours after opening a ticket explaining the problem and giving the URL, I received a reply asking for a URL! - terrific! I think support might find their job easier if they actually read the tickets in the first place.