When you perform any OS defragmentation or virus scan operations, please make sure mysql is shutdown. No utilities (mysql-based or otherwise) should be running against any table while the server is up. MySQL is not good to run on a PC that is not dedicated to MySQL DB only, especially in the presence of defragmentation or virus scan software running. Temp tables have also been known to get whacked by virus scan software.
At the very least, move the MyISAM table to a folder away from the standard datadir.
You should consider defragmenting the MyISAM table using:
OPTIMIZE TABLE calllog;
or you can do it in stages:
CREATE TABLE calllognew LIKE calllog;
ALTER TABLE calllognew DISABLE KEYS;
INSERT INTO calllognew SELECT * FROM calllog;
ALTER TABLE calllognew ENABLE KEYS;
ALTER TABLE calllog RENAME calllogold;
ALTER TABLE calllognew RENAME calllog;
DROP TABLE calllogold;
You may need to consider upgrading to MySQL 5.5 for the latest MyISAM storage engine code.
If you want to switch to InnoDB, you must configure it so that each table has its own tablespace.
SQL Server Management Studio Startup
When Microsoft's SQL Server Management Studio (SSMS) starts it tries to connect the Certificate Revocation List (CRL) of Microsoft:
http://crl.microsoft.com/pki/crl/products/MicrosoftRootAuthority.crl
The underlying .NET components of SSMS are trying to contact the Certificate Revocation List and SSMS is unable to do so. This slows down the overall loading procedure. (15 seconds per certificate apparently)
Ok so here is what is happening. SSMS has a high percentage of managed code, all of this code is signed when we ship it. At start up (if this setting is checked) the .Net Runtime tries to contact crl.microsoft.com to ensure that the cert is valid(there were some fake certs issued in Microsoft’s name a while back so this is a very valid concern). If there is no internet connection or there is a problem contacting the certificate revocation list server then this will delay SSMS startup.
Reference: FAQ, Why does SSMS take 45s to start up? (MSDN Blog)
One issue that can cause this problem is that if the server does not have access to the internet, then the .NET framework can’t access the crl.microsoft.com website to verify that the digital signatures used to sign the binaries for managed applications are valid. Each certificate check has a 15 second timeout in the .NET runtime implementation. Depending on what features are installed, this can add up to a minute of startup time for Management Studio.
Reference: SQL Server Management Studio Startup Time (MSDN Blog)
Solutions
You can circumvent part of the issue, by downloading the certificate directly be entering the link into your browser and then importing the certificate to your certificate database
You can reconfigure your (company's) firewall to allow connections to Microsoft's CRL
You can reconfigure your personal antivirus/firewall to allow connections to the Microsoft CRL
You can configure your (company's) firewall to send a timeout faster to your client for requests accessing Microsoft's CRL.
You can configure IE to no longer "Check publisher's certificate revocation" in the advanced settings.
(See above mentioned blogs 1 and 2 for details)
Best Answer
To prevent SQL Server updates to be installed automatically, you need to:
Important: choose "Manual", NOT "DownloadOnly", because even with "DownloadOnly" setting, some Windows Updates that Microsoft considers very important, may be still installed and machine will be rebooted (I've experienced it myself)
This way you have total control over when and how to install Windows and SQL Server updates