I am running MySQL 5.5.29 on Windows 2008 R2 Server. The server has a mix of MyISAM & InnoDB tables with InnoDB being the default database engine. Looking at the servers configuration settings in MySQL Workbench, I can see that the “default-storage-engine=INNODB” under the General tab. However, if I look under the INNODB tab I see an option “InnoDB” that is set to “OFF”. There is a checkbox next to this setting, but it is not selected. Possible values for this option are “ON”, “OFF” & “FORCE”.
It would appear from the startup log that InnoDB is started, but I don’t understand the purpose of the “InnoDB” option. Does this need to be enabled for InnoDB to function properly? The only thing I read about this was in regard to the “FORCE” option, which basically prevent the server from starting without InnoDB support. If I don’t want to use the FORCE option, what is the relevance of the ON/OFF setting in relationship to the “default-storage-engine” setting under the General tab?
Can someone also confirm that the reason the log file lists “The InnoDB memory heap is disabled” is because the “innodb_use_sys_malloc” is enabled?
Thanks
130226 6:20:01 [Note] Plugin 'FEDERATED' is disabled.
130226 6:20:01 InnoDB: The InnoDB memory heap is disabled
130226 6:20:01 InnoDB: Mutexes and rw_locks use Windows interlocked functions
130226 6:20:01 InnoDB: Compressed tables use zlib 1.2.3
130226 6:20:01 InnoDB: Initializing buffer pool, size = 4.0G
130226 6:20:02 InnoDB: Completed initialization of buffer pool
130226 6:20:02 InnoDB: highest supported file format is Barracuda.
130226 6:20:02 InnoDB: Waiting for the background threads to start
130226 6:20:03 InnoDB: 1.1.8 started; log sequence number 21927692691
130226 6:20:03 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
130226 6:20:03 [Note] - '0.0.0.0' resolves to '0.0.0.0';
130226 6:20:03 [Note] Server socket created on IP: '0.0.0.0'.
130226 6:20:03 [Note] Event Scheduler: Loaded 0 events
130226 6:20:03 [Note] D:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: ready for connections.
Version: '5.5.29-log' socket: '' port: 3306 MySQL Community Server (GPL)
It would appear from the startup log that InnoDB is started, but I don’t understand the purpose of the “InnoDB” option. Does this need to be enabled for InnoDB to function properly? The only thing I read about this was in regard to the “FORCE” option, which basically prevent the server from starting without InnoDB support. If I don’t want to use the FORCE option, what is the relevance of the ON/OFF setting in relationship to the “default-storage-engine” setting under the General tab?
Can someone also confirm that the reason the log file lists “The InnoDB memory heap is disabled” is because the “innodb_use_sys_malloc” is enabled?
Thanks
130226 6:20:01 [Note] Plugin 'FEDERATED' is disabled.
130226 6:20:01 InnoDB: The InnoDB memory heap is disabled
130226 6:20:01 InnoDB: Mutexes and rw_locks use Windows interlocked functions
130226 6:20:01 InnoDB: Compressed tables use zlib 1.2.3
130226 6:20:01 InnoDB: Initializing buffer pool, size = 4.0G
130226 6:20:02 InnoDB: Completed initialization of buffer pool
130226 6:20:02 InnoDB: highest supported file format is Barracuda.
130226 6:20:02 InnoDB: Waiting for the background threads to start
130226 6:20:03 InnoDB: 1.1.8 started; log sequence number 21927692691
130226 6:20:03 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
130226 6:20:03 [Note] - '0.0.0.0' resolves to '0.0.0.0';
130226 6:20:03 [Note] Server socket created on IP: '0.0.0.0'.
130226 6:20:03 [Note] Event Scheduler: Loaded 0 events
130226 6:20:03 [Note] D:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: ready for connections.
Version: '5.5.29-log' socket: '' port: 3306 MySQL Community Server (GPL)