Binary Logging Option for MySQL

MySQL offers Binary Logging, an advanced feature that captures changes between backups and stores this information in binary log files. The log files—containing information about each statement that modified (or might have modified) the database and the amount of time it took to make the change—are mainly used for data recovery and replication efforts. The files reside in either location:

• The /var/lib/mysql directory on Linux

• The program data directory on Windows (for example, C\ProgramData\MySQL\MySQL Server 8.0\Data)

Possible Issues with Binary Logging

Binary Logging can cause issues when a Code Insight Electronic Update or scan is run. During either of these processes, the database can be updated with a significant number of insert, update, and delete events. With Binary Logging enabled, details for each event are also written to rolling binary log files, with each file being about 1 GB in size. If these log files are not purged regularly, out-of-memory issues will occur.

The user can decide whether Binary Logging should be enabled.

Disabling or Enabling Binary Logging

By default, Binary Logging is enabled in MySQL8, but disabled in MySQL5.

To disable or enable Binary Logging, do the following:

1. Within your MySQL installation, do one of the following:

   • As root user in Linux, open the my.cnf file (typically located in /etc/).

   • As a Windows administrator, open my.ini file (typically located in C:\ProgramData\MySQL\MySQL Server``version).

2. To enable Binary Logging, add or uncomment the log-bin line:

   • #Binary Logging
     log-bin=“<binaryLogBaseName>”

   • or

   • To disable Binary Logging, comment-out the log-bin line:

   • #Binary Logging
     #log-bin=“<binaryLogBaseName>”

3. Restart the database server.