Difficulty: Easy
Correct Answer: Invalid (MySQL stores metadata in information_schema and related system schemas, not “meta_sql”)
Explanation:
Introduction / Context: Understanding where a DBMS stores metadata helps DBAs query object definitions, privileges, and performance statistics. MySQL provides well-known system schemas for this purpose; confusing their names may lead to incorrect administrative queries.
Given Data / Assumptions:
Concept / Approach: MySQL uses several system schemas: information_schema (virtual metadata views), performance_schema (instrumentation), and the mysql schema (users, privileges, time zone tables, and other internal data). There is no standard schema named “meta_sql.” Therefore, the statement is incorrect.
Step-by-Step Solution:
List system schemas in a stock MySQL instance: information_schema, performance_schema, mysql, sys (helper views).Identify that metadata about tables, columns, and routines is obtained from information_schema views.Conclude that “meta_sql” is not a MySQL system database.Therefore, the claim is invalid.Verification / Alternative check: Run SHOW DATABASES; inspect the presence of the documented system schemas and the absence of “meta_sql.”
Why Other Options Are Wrong:
Common Pitfalls: Confusing MySQL system schemas with SQL Server’s system databases or assuming custom admin-created schemas are universal.
Final Answer: Invalid (MySQL stores metadata in information_schema and related system schemas, not “meta_sql”)
Discussion & Comments