Cloud DB Scanner usage examples

Available in VPC

Scenario overview

Describes the process of scanning the schema of the source data you want and creating a table by creating a scanner targeting Cloud DB for MySQL.

Source data

The source data stored in Cloud DB for MySQL consists of air pollution measurement data, including various measurement information such as date and time, monitoring station, ozone concentration, and sulfur dioxide concentration.

Data examples

Create and run scanner

Create connection

# Basic information
Name: (atmosphere-mysql-connection)

# Source data
Data type: (Cloud DB for MySQL)
DB service: (DB service name of the user's Cloud DB for MySQL)
Database: (name of the database to be scanned in the DB service)

# Create account
User name: (DB account name to be used to access Cloud DB for MySQL)
Password: (DB password to be used to access Cloud DB for MySQL)

• Create Account>User Name/Password: Create a new DB account to access source data. The newly created account is granted read-only permission which can be limitedly accessed from Data Catalog only.

Create scanner

# Source data
Data type: (Cloud DB for MySQL)
Connection: (atmosphere-mysql-connection)
Path: (not entered)

# Execution option
Cycle: (on demand)
Pattern: (not used)

• Path: When entering a value, it is automatically processed as 'corresponding value + %'. Among the tables in the database for scanning, tables with names starting with the value are scanned.
• Pattern: When specific patterns are included/excluded, only tables with the names of the patterns can be scanned. If patterns are not used, all tables in the selected database path are scanned.

If both path and pattern conditions are set, among the tables meeting the path and the pattern condition, tables that satisfy the pattern condition are scanned.

# Output data
Database: (default)
Prefix: (not entered)
When adding a schema: (update table definition)

• prefix: A prefix is added to the output data table name to distinguish itself from output data of other scans.

• When adding a schema

  • Update table definition: When scanning, every detail related to the table change is updated.
  • Add only new columns: Updates are performed when scanning only if columns are added to the table, and deleted columns are ignored.
  • Ignore: ignore all table changes when scanning.

Run scanner

• Start scanning by pressing the [Run] button on the scanner waiting to run.
• The scanner in the Start running state changes to the Standby state as soon as the scan is completed.
• You can check the results in the History tab and the schema in the Table menu.

Schema run result