Help from the people who build it
Most questions are answered in the documentation. When they are not, email reaches the product team directly.
Documentation
Installation, activation, connections, comparison options, deployment and troubleshooting — written to be read before something goes wrong.
Email support
Answered by the people who build the product, not a first-line queue. Include your version number and MySQL server version for a faster answer.
Report an issue
Found a bug, a wrong comparison result, or a generated statement that fails? Send us the details below and we will reproduce it.
Answers to what people ask most
Grouped by where in the process the question tends to come up.
Installation
Activation
Connections
Comparing
Deploying
What to send us
A report with these five things in it can usually be reproduced the same day. Without them it turns into several rounds of questions.
Version numbers
The SchemaSync version from Help ▸ About, and your MySQL or MariaDB server version.
What you expected, and what happened
One sentence each is enough. If a comparison result looks wrong, tell us what you believe the correct answer is.
The object definition
For a comparison or generated-SQL problem, the `SHOW CREATE` output for the object from both databases.
The exact error
The full message, including any MySQL error number. A screenshot of the dialog works.
The diagnostics log
Help ▸ Diagnostics writes it to `%APPDATA%\SchemaSync\logs`. Credentials are redacted, but read it before sending — it contains your object names.
-- The object definition, exactly as the server reports itSHOW CREATE TABLE `your_table`; -- Server version and the settings that most often explain a differenceSELECT VERSION();SHOW VARIABLES LIKE 'character_set_server';SHOW VARIABLES LIKE 'collation_server';SHOW VARIABLES LIKE 'sql_mode';Please do not send us credentials
We never need a username, password or a live connection to diagnose a problem. Object definitions and the log are enough. If you believe you have found a security issue, email security@schemasync.in rather than using a public channel.