Grant Tables contain scope columns indicating tables or table/column combinations to which each row applies. The procs_priv  scope columns indicate the stored routine to which each row applies. •Privilege columns indicate which privileges a table row grants; that is, which operations it permits to be performed. The server combines the information in the various grant tables to form a complete description of a user’s privileges. Section 6.2.7, “Access Control, Stage 2: Request Verification” , describes the rules for this. In addition, a grant table may contain columns used for purposes other than scope or privilege assessment. The server uses the grant tables in the following manner: •The  user  table scope columns determine whether to reject or permit incoming connections. For permitted connections, any privileges granted in the  user  table indicate the user’s static global privileges. Any privileges granted in this table apply to  all  databases on the server. Caution Because any static global privilege is considered a privilege for all databases, any static global privilege enables a user to see all database names with  SHOW DATABASES  or by examining the  SCHEMATA  table of  INFORMATION_SCHEMA , except databases that have been restricted at the database level by partial revokes. •The  global_grants  table lists current assignments of dynamic global privileges to user accounts. For each row, the scope columns determine which user has the privilege named in the privilege column. •The  db  table scope columns determine which users can access which databases from which hosts. The privilege columns determine the permitted operations. A privilege granted at the database level applies to the database and to all objects in the database, such as tables and stored programs. •The  tables_priv  and  columns_priv  tables are similar to the  db  table, but are more fine-grained: They apply at the table and column levels rather than at the database level. A privilege granted at the table level applies to the table and to all its columns. A privilege granted at the column level applies only to a specific column. •The  procs_priv  table applies to stored routines (stored procedures and functions). A privilege granted at the routine level applies only to a single procedure or function. •The  proxies_priv  table indicates which users can act as proxies for other users and whether a user can grant the  PROXY  privilege to other users. •The  default_roles  and  role_edges  tables contain information about role relationships. •The  password_history  table retains previously chosen passwords to enable restrictions on password reuse. See Section 6.2.15, “Password Management” . The server reads the contents of the grant tables into memory when it starts. You can tell it to reload the tables by issuing a  FLUSH PRIVILEGES  statement or executing a  mysqladmin flush-privileges  or mysqladmin reload  command. Changes to the grant tables take effect as indicated in Section 6.2.13, “When Privilege Changes Take Effect” . When you modify an account, it is a good idea to verify that your changes have the intended effect. To check the privileges for a given account, use the  SHOW GRANTS  statement. For example, to determine the privileges that are granted to an account with user name and host name values of  bob  and pc84.example.com , use this statement: 1206