zoukankan      html  css  js  c++  java
  • A better SHOW TABLE STATUS

    From command line we have the entire MySQL server on hands (if we have privileges too of course) but we don’t have a overall overview, at this point the show table status command is every useful, or not?.

    This is what we get when run show table status in a standard 80×25 terminal screen:

    We can maximize the terminal window and decrease font size, but not all the time we need that lots of info. Some time ago I develop a stored procedure to get a global overview including functions and stored procedures. The result is pretty comprehensible:

    call tools.sp_status(database());
    +----------------------------+--------+-------+---------+-----------------+
    | Table Name                 | Engine | Rows  | Size    | Collation       |
    +----------------------------+--------+-------+---------+-----------------+
    | actor                      | InnoDB | 200   | 0.03 Mb | utf8_general_ci |
    | actor_info                 | [VIEW] | -     | -       | -               |
    | address                    | InnoDB | 589   | 0.09 Mb | utf8_general_ci |
    | category                   | InnoDB | 16    | 0.02 Mb | utf8_general_ci |
    | city                       | InnoDB | 427   | 0.06 Mb | utf8_general_ci |
    | country                    | InnoDB | 109   | 0.02 Mb | utf8_general_ci |
    | customer                   | InnoDB | 541   | 0.12 Mb | utf8_general_ci |
    | customer_list              | [VIEW] | -     | -       | -               |
    | film                       | InnoDB | 1131  | 0.27 Mb | utf8_general_ci |
    | film_actor                 | InnoDB | 5143  | 0.27 Mb | utf8_general_ci |
    | film_category              | InnoDB | 316   | 0.08 Mb | utf8_general_ci |
    | film_list                  | [VIEW] | -     | -       | -               |
    | film_text                  | MyISAM | 1000  | 0.31 Mb | utf8_general_ci |
    | inventory                  | InnoDB | 4673  | 0.36 Mb | utf8_general_ci |
    | language                   | InnoDB | 6     | 0.02 Mb | utf8_general_ci |
    | nicer_but_slower_film_list | [VIEW] | -     | -       | -               |
    | payment                    | InnoDB | 15422 | 2.12 Mb | utf8_general_ci |
    | rental                     | InnoDB | 15609 | 2.72 Mb | utf8_general_ci |
    | sales_by_film_category     | [VIEW] | -     | -       | -               |
    | sales_by_store             | [VIEW] | -     | -       | -               |
    | staff                      | InnoDB | 1     | 0.09 Mb | utf8_general_ci |
    | staff_list                 | [VIEW] | -     | -       | -               |
    | store                      | InnoDB | 2     | 0.05 Mb | utf8_general_ci |
    +----------------------------+--------+-------+---------+-----------------+
    23 rows in set (0.04 sec)
     
    +----------------------------+-----------+---------------------+
    | Routine Name               | Type      | Comment             |
    +----------------------------+-----------+---------------------+
    | get_customer_balance       | FUNCTION  |                     |
    | inventory_held_by_customer | FUNCTION  |                     |
    | inventory_in_stock         | FUNCTION  |                     |
    | film_in_stock              | PROCEDURE |                     |
    | film_not_in_stock          | PROCEDURE |                     |
    | rewards_report             | PROCEDURE |                     |
    | customer_create_date       | TRIGGER   | On INSERT: customer |
    | del_film                   | TRIGGER   | On DELETE: film     |
    | ins_film                   | TRIGGER   | On INSERT: film     |
    | payment_date               | TRIGGER   | On INSERT: payment  |
    | rental_date                | TRIGGER   | On INSERT: rental   |
    | upd_film                   | TRIGGER   | On UPDATE: film     |
    +----------------------------+-----------+---------------------+
    12 rows in set (0.04 sec)
     
    Query OK, 0 rows affected (0.04 sec)

    There is the procedure source code:

    DELIMITER $$
    DROP PROCEDURE IF EXISTS `tools`.`sp_status` $$
    CREATE PROCEDURE `tools`.`sp_status`(dbname VARCHAR(50))
    BEGIN 
    -- Obtaining tables and views
    (
        SELECT 
         TABLE_NAME AS `Table Name`, 
         ENGINE AS `Engine`,
         TABLE_ROWS AS `Rows`,
         CONCAT(
            (FORMAT((DATA_LENGTH + INDEX_LENGTH) / POWER(1024,2),2))
            , ' Mb')
           AS `Size`,
         TABLE_COLLATION AS `Collation`
        FROM information_schema.TABLES
        WHERE TABLES.TABLE_SCHEMA = dbname
              AND TABLES.TABLE_TYPE = 'BASE TABLE'
    )
    UNION
    (
        SELECT 
         TABLE_NAME AS `Table Name`, 
         '[VIEW]' AS `Engine`,
         '-' AS `Rows`,
         '-' `Size`,
         '-' AS `Collation`
        FROM information_schema.TABLES
        WHERE TABLES.TABLE_SCHEMA = dbname 
              AND TABLES.TABLE_TYPE = 'VIEW'
    )
    ORDER BY 1;
    -- Obtaining functions, procedures and triggers
    (
        SELECT ROUTINE_NAME AS `Routine Name`, 
         ROUTINE_TYPE AS `Type`,
         '' AS `Comment`
        FROM information_schema.ROUTINES
        WHERE ROUTINE_SCHEMA = dbname
        ORDER BY ROUTINES.ROUTINE_TYPE, ROUTINES.ROUTINE_NAME
    )
    UNION
    (
        SELECT TRIGGER_NAME,'TRIGGER' AS `Type`, 
        concat('On ',EVENT_MANIPULATION,': ',EVENT_OBJECT_TABLE) AS `Comment`
        FROM information_schema.TRIGGERS
        WHERE EVENT_OBJECT_SCHEMA = dbname
    )
    ORDER BY 2,1;
    END$$
    DELIMITER ;

    To use in your place you must call as:

    mysql> call tools.sp_status(database());

    Note the stored procedure has created in tools database (you can use another db), the goal of this is to call that useful procedure from any database, and it receives the name of database as parameter because is not possible obtain the current database from inside of stored procedure.

    参考:

    http://en.latindevelopers.com/ivancp/2012/a-better-show-table-status/

  • 相关阅读:
    关于unity的一个不错的插件平台
    erlang otp中的socket参数设置
    android开发国内镜像
    composer中文镜像
    bootstrap的一些资源
    根据现有表操作基于active record的model
    Erlang Web 监控工具
    erlang程序发布的时候需要注意的地方
    pcl学习笔记(二):点云类型
    c++中inline函数的意义
  • 原文地址:https://www.cnblogs.com/xiaotengyi/p/4158919.html
Copyright © 2011-2022 走看看