The Root Causes of Database Table Corruption

From support-works
Revision as of 15:39, 19 January 2018 by Deenc (talk | contribs) (Created page with "{{Template:Basic Cover |title=The Root Causes of Database Table Corruption |type=FAQ |htl=Y }} {{Template:Basic Status |status=Published |version=1.0 |authors=HTL QA |applica...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search



Status: Published
Version: 1.0
Authors: HTL QA
Applies to: Core Services Version 3.x and above


Virus Scanners - 3rd Party Backup software - Shadow copy service - cause of table corruption

How Virus Scanners, Backup software and the Shadow copy service cause table corruption.

The SwSQL database is based on MySQL and uses the MyISAM engine. MySQL uses three files (*.frm,*.MYI and *.MYD) to represent each table and the engine implements table level locking. This means that when a table is updated no one else can access the table as all of the table files are locked to avoid corruption of the data.

Table corruption occurs when another application other than the SwSQLServer has already locked either the Data file or the Index file when SwSQL locks the table for update.

The types of application that will lock the database files are typically either Anti Virus, Backup or the Windows Shadow Copy Service.

Therefore to avoid table corruption we would advise that the Hornbill folder be added to the exception list of any Anti Virus or Backup software that runs automatically on the server.

We would also advise that the Drive that the Supportworks Server is installed on be added to the exception list of the Windows Shadow Copy Service.