Read Caching & Opportunistic Locking

Many types of data corruption can result from improperly configured networks. Typical data corruption caused by such configuration problems is index corruption, but such corruption can be worse than this and affect the entire database, not just indexes.

These problems typically affect file system databases, such as the embedded (DataFlex) database. The best recommendation for avoiding these problems is to use a client/server database, such as Microsoft SQL Server, instead of the embedded database on networks, particularly Microsoft Windows networks. DataFlex includes database drivers for many databases including Microsoft SQL Server, IBM's DB2 Universal Database, and any ODBC-compliant database.

Microsoft Windows Networks

Improperly configured Windows networks can lead to data corruption in any file system database, including the embedded (DataFlex) database. Two Windows networking behaviors, opportunistic locking (on Windows servers) and read caching (on Windows clients), are the source of the corruption potential.

Data Access Worldwide has a white paper titled "Opportunistic Locking and Read Caching on Microsoft Windows Networks" that explains how to properly configure Windows Networks for use with the embedded (DataFlex) database. This white paper is available from the white papers section of the Data Access Worldwide website.

Check the Microsoft Windows documentation for more information regarding read caching on Windows networks.