The -N or –skip-column-names is a convenient option with the mysql client to skip the header line of output.
However I found when viewing the output via the terminal, some interesting and unexplained output.
$ mysql -h*** -u*** -p -e "SELECT VARIABLE_NAME,VARIABLE_VALUE FROM INFORMATION_SCHEMA.GLOBAL_STATUS" +--------------------------------+----------------+ | VARIABLE_NAME | VARIABLE_VALUE | +--------------------------------+----------------+ | ABORTED_CLIENTS | 710001 | | ABORTED_CONNECTS | 31 | | BINLOG_CACHE_DISK_USE | 0 | | BINLOG_CACHE_USE | 0 | | BYTES_RECEIVED | 2522301004 | | BYTES_SENT | 317785976 | | COM_ADMIN_COMMANDS | 2890667 | | COM_ASSIGN_TO_KEYCACHE | 0 | | COM_ALTER_DB | 0 | | COM_ALTER_DB_UPGRADE | 0 |
$ mysql -N -h*** -u*** -p -e "SELECT VARIABLE_NAME,VARIABLE_VALUE FROM INFORMATION_SCHEMA.GLOBAL_STATUS" +--------------------------------+--------------+ | ABORTED_CLIENTS | 710001 | | ABORTED_CONNECTS | 31 | | BINLOG_CACHE_DISK_USE | 0 | | BINLOG_CACHE_USE | 0 | | BYTES_RECEIVED | 2522947764 | | BYTES_SENT | 348838502 | | COM_ADMIN_COMMANDS | 2890742 |
As you can see all the values of the first column are right aligned in terminal display. When written to a file (which is the intended outcome), the data is not.
$ mysql ... > /tmp/x $ head /tmp/x ABORTED_CLIENTS 710009 ABORTED_CONNECTS 31 BINLOG_CACHE_DISK_USE 0 BINLOG_CACHE_USE 0 BYTES_RECEIVED 2526760299 BYTES_SENT 530046795 COM_ADMIN_COMMANDS 2890742 COM_ASSIGN_TO_KEYCACHE 0 COM_ALTER_DB 0 COM_ALTER_DB_UPGRADE 0