A. Per transaction

B. Globally

C. Per session

D. Per user name

A. be run once the table reaches 100,000 rows or above

B. be run when EXPLAIN SELECT shows that an inordinate amount of rows is expected to be read during query execution

C. be run when you suspect that a table is heavily fragmented

D. be run when more than 5% of the rows are changed by a single statement

E. generally never be run manually

A. The time taken to read & write table rows on disk.

B. Syntax when writing queries involving JOINs

C. Memory usage.

D. Disk usage when storing data.

A. Neither mysqlcheck or myisamchk can perform checks and repairs on a remote server.

B. mysqlcheck must run on the server to perform checks and repairs and myisamchk can perform checks and repairs on a remote server.

C. Both mysqlcheck and myisamchk can perform checks and repairs on a remote server.

D. mysqlcheck can perform checks and repairs on a remote server, and myisamchk must run on the server.

A. c:\MySQL

B. Below the MySQL data directory.

C. Below the MySQL installation directory.

D. /usr/share/mysql

A. To make sure that no table data are corrupted.

B. to improve performance by updating index distribution statistics on InnoDB tables.

C. To repair table structure problems.

D. To find out why a query takes a long time to execute on a given table.

E. To make sure a table has no structural problems.

A. They can support transactions.

B. They can not contain TEXT or BLOB columns

C. Each table is represented on disk as a .frm file.

D. Each table has a corresponding .MYI and .MYD file.

E. They can support foreign keys.

F. Table contents will not be saved if the server is restarted.

A. --start-position will read the binlog entries starting at the specified position

B. --end-datetime will read the binlog entries up to the specified date and time

C. --end-position will read the binlog entries up to the specified position

D. --start-datetime will read the binlog entries starting at the specified date and time

E. --start-file will read the binlog entries starting with the specified filename

F. --end-file will read the binlog entries ending after the specified filename

A. None of the above

B. Update table pets

C. SELECT from table pets

D. UPDATE and SELECT from table pets

A. It locks a table for reading but allows concurrent inserts.

B. It locks a table for writing, preventing reads until it is released.

C. It locks a table for reading only by connections on localhost.