Skip to main content
The MySQL integration sends Octoparse task results to a MySQL database. Use it when extracted data needs to be stored in a structured database for applications, reporting, automation, or internal data workflows.

​
When to use MySQL

Use MySQL when:
  • Data needs to be queried by applications or BI tools
  • Spreadsheet exports are not scalable enough
  • You need recurring structured storage
  • Teams need a shared database destination
  • Data should feed an existing relational workflow

​
Setup workflow

1

Prepare the database

Create or identify the target database and table structure.
2

Confirm network access

Make sure Octoparse can reach the database host and port.
3

Map fields

Match Octoparse output fields to database columns.
4

Test with sample data

Export a small result set and verify column mapping, data types, and encoding.
5

Enable recurring export

Use scheduled runs only after the database export is verified.

​
Before exporting

Check:
AreaWhat to verify
Host and portDatabase is reachable from the export environment
CredentialsUser has permission to insert or update data
Table schemaColumns match the task output
Data typesText, numbers, dates, and URLs fit the destination columns
DuplicatesExport behavior does not create unwanted repeated rows
EncodingSpecial characters are stored correctly
Database exports should be tested carefully. Incorrect field mapping or duplicate handling can affect downstream systems that depend on the database.