content_image/830333.jpg content_image/830330.jpg content_image/830334.jpg content_image/830331.jpg content_image/830332.jpg
CREATE TABLE D ... ENGINE NDB; ALTER TABLE C ENGINE NDB; SET @@ndb_table_no_logging = 1; 

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. 

<img src='content_image/830333.jpg'>

• ndb_table_temporary 

## Note 

ndb_table_no_logging  has no effect on the creation of NDB  table schema files; to suppress these, use ndb_table_temporary  instead. 

<img src='content_image/830330.jpg'>

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. 

<img src='content_image/830334.jpg'>

• ndb_use_copying_alter_table 

## Note 

Setting this variable currently has no effect. This is a known issue; see Bug #34036. 

<img src='content_image/830331.jpg'>

Forces NDB  to use copying of tables in the event of problems with online ALTER TABLE  operations. The default value is OFF . 

• ndb_use_exact_count 

<img src='content_image/830332.jpg'>

