All Products
Search

This Product

    AnalyticDB:Manage built-in datasets

    Document Center

    AnalyticDB:Manage built-in datasets

    Last Updated:Dec 02, 2025

    AnalyticDB for MySQL lets you load built-in datasets to quickly test your AnalyticDB for MySQL clusters. You can load a built-in dataset automatically when you create a cluster or manually from the console. This topic describes how to load and delete built-in datasets.

    Precautions

    • Only Enterprise Edition, Basic Edition, and Data Lakehouse Edition clusters support loading built-in datasets.

      You can use the built-in dataset to quickly test a cluster. For more information, see TPC-H test set.

      Note

      The built-in dataset is approximately 10 GB, whereas the tables created in the TPC-H test are approximately 1 TB. Therefore, testing a cluster with the built-in dataset reflects its performance only for a 10 GB data volume.

    • Standard database accounts cannot load, use, or delete the dataset because they do not have permissions on the ADB_Internal_TPCH_10GB database. A privileged account must grant permissions to the standard account. The authorization statement is GRANT select ON ADB_Internal_TPCH_10GB.* TO <user_name>;.

    • The built-in dataset is approximately 10 GB. You are not billed for the storage space that this data occupies.

    • Loading the built-in dataset takes approximately 6 to 8 minutes. This process consumes reserved compute resources from the `user_default` resource group. Ensure that the `user_default` resource group has at least 16 ACU of reserved compute resources for the data initialization.

    • Ensure that the cluster has at least 24 ACU of reserved storage resources. Otherwise, loading the built-in dataset will fail.

    • A database named ADB_Internal_TPCH_10GB cannot exist in the cluster. If a database with this name already exists, the dataset load will fail.

    • If you delete one or more tables from the built-in dataset, some of the associated scripts may become unavailable. To resolve this issue, delete the entire database for the built-in dataset and then reload it.

    Manually load the built-in dataset

    1. Log on to the AnalyticDB for MySQL console. In the upper-left corner of the console, select a region. In the left-side navigation pane, click Clusters. Find the cluster that you want to manage and click the cluster ID.

    2. In the left-side navigation pane, choose Job Development > SQL Development.

    3. Click Load Built-in Dataset.

      After the built-in dataset is created, the Load Built-in Dataset button is disabled. You can then view the ADB_Internal_TPCH_10GB database and its tables on the Databases and Tables tab.

      Note

      For more information about the tables in the built-in dataset, see Create test tables.

    Delete the built-in dataset

    To delete the built-in dataset, you must first delete all tables within the ADB_Internal_TPCH_10GB database. Run the DROP TABLE table_name; SQL statement for each table. After all tables are deleted, run the DROP DATABASE ADB_Internal_TPCH_10GB; SQL statement to delete the database.

    When you delete the database, the associated scripts are also deleted.

    FAQ

    • Q: What are the prerequisites for a cluster to load the built-in dataset?

      A: The cluster must have at least 24 ACU of reserved storage resources, and the user_default resource group must have at least 16 ACU of reserved compute resources.

    • Q: How do I know if the built-in dataset was loaded successfully?

      A: Navigate to Job Development > SQL Development to view the loading progress. The dataset is loaded successfully if an 1 icon appears next to Load Built-in Dataset, the option is disabled, and you can view the ADB_Internal_TPCH_10GB database and its tables on the Databases and Tables tab.

    • Q: What should I do if the loading fails or takes a long time?

      A: Delete all tables in the database by running the DROP TABLE table_name; SQL statement for each table. Then, delete the database by running the DROP DATABASE ADB_Internal_TPCH_10GB; SQL statement. After the ADB_Internal_TPCH_10GB database is deleted, load the dataset again.

    • Q: How can a standard database account use the built-in dataset feature?

      A: The built-in dataset feature adheres to the permission management rules of AnalyticDB for MySQL. A standard database account cannot use the built-in dataset unless a privileged account grants it permissions on the ADB_Internal_TPCH_10GB database. The authorization statement is:

      GRANT select ON ADB_Internal_TPCH_10GB.* TO <user_name>;

    • Q: After the built-in dataset is loaded, how do I test it?

      A: After the dataset is loaded, AnalyticDB for MySQL provides default query scripts. You can run these sample query statements from the Scripts tab on the SQL Development page. For more information about the query statements, see TPC-H test set.

      Important

      To ensure the integrity of the dataset, perform only query operations on the ADB_Internal_TPCH_10GB database. If the dataset becomes corrupted due to Data Definition Language (DDL) or Data Manipulation Language (DML) operations, delete the ADB_Internal_TPCH_10GB database and reload the dataset.

    References