NDB Cluster Configuration Files After the previous sequence of events, tables  A  and  B  are not checkpointed;  A  was created with  ENGINE NDB  and B was altered to use  NDB , both while  ndb_table_no_logging  was enabled. However, tables  C  and  D  are logged;  C  was altered to use  NDB  and  D  was created using  ENGINE NDB , both while ndb_table_no_logging  was disabled. Setting  ndb_table_no_logging  back to  1  or  ON  does  not cause table  C  or  D  to be checkpointed. ndb_table_no_logging  has no effect on the creation of  NDB  table schema files; to suppress these, use  ndb_table_temporary  instead. When set to  ON  or  1 , this variable causes  NDB  tables not to be written to disk: This means that no table schema files are created, and that the tables are not logged. Setting this variable currently has no effect. This is a known issue; see Bug #34036. 4192 • ndb_use_exact_count Forces  NDB  to use copying of tables in the event of problems with online  ALTER TABLE  operations. The default value is  OFF . • ndb_use_copying_alter_table • ndb_table_temporary CREATE TABLE D ... ENGINE NDB; ALTER TABLE C ENGINE NDB; SET @@ndb_table_no_logging = 1; Note Note System Variable ndb_table_temporary Scope Session Dynamic Yes SET_VAR  Hint Applies No Type Boolean Default Value OFF System Variable ndb_use_copying_alter_table Scope Global, Session Dynamic No SET_VAR  Hint Applies No System Variable ndb_use_exact_count Scope Global, Session Dynamic Yes SET_VAR  Hint Applies No Type Boolean