> ## Documentation Index
> Fetch the complete documentation index at: https://www.docusnap.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Scanning MySQL Server

> Capturing MySQL servers and their databases—with users, plugins, tables and routines.

The *MySQL Server* scan module captures MySQL servers and their databases. It
requires a connected [gateway](/docs/en/scan/gateway-install).

## Captured data

The scan creates assets of these two types:

| Type | Groups |
| - | - |
| *MySQL Server* | Database Details (Users, Engines, Plugins, Databases) |
| *MySQL Database* | Database Details (Tables, Views, Events, Routines, Trigger) |

How the detail pages of the types are structured is described in
[Databases](/docs/en/assets/databases).

## Setting up the job

The wizard follows the standard path *Basics* › *Targets* › *Schedule* ›
*Summary*—see [Creating a Scan Job](/docs/en/scan/create-inventory). The
*Targets* step is what sets this module apart.

Each row carries four columns:

| Column | Content |
| - | - |
| *IP/Hostname* | one MySQL server as an address or hostname |
| *Credentials* | an entry of the type *User Account* |
| *Port* | the server's port, prefilled with 3306 |
| *Also Capture Object Details* | per target, off by default |

The *Credentials* column must be filled. An entry in
*Credentials for all targets* applies to every row without an assignment of
its own.

## Related

After it is created, the job appears among the jobs; how you watch and adjust
it is in [Managing Jobs](/docs/en/scan/manage-jobs). Fields, values and bounds for
looking up are in the [Scan Reference](/docs/en/scan/reference).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.