Troubleshooting & FAQ - Cloud Database (Legacy V1)

Below you will find answers to common technical questions regarding the V1 Cloud Database platform.

1. Maintenance Schedule

Because this is a managed service, Tilaa handles all patching and upgrades of the database software.

• Planning: Maintenance is carefully planned to minimize impact.
• Notification: You will receive an email notification well in advance with the scheduled time window.

2. Slow Connections (IPv6 Timeout)

Symptom: Establishing a connection to the database takes several seconds (or minutes), but once connected, queries run fast.

Cause:
Modern operating systems prefer IPv6. If your application server has an IPv6 address, it will try to connect via IPv6 first. If this IP is not whitelisted in the Cloud Database firewall, the connection hangs until it times out and falls back to IPv4.

Solution:
Ensure you provide Support with both your IPv4 and IPv6 addresses to be whitelisted. This ensures an instant connection regardless of the protocol used.

3. SQL Syntax Error (Double Quotes)

Error: ERROR 1064 (42000): ... near '"tablename"' at line 1

Cause:
By default, MySQL uses backticks (` ) to quote identifiers (table names, columns). Using double quotes (") is interpreted as a string, not an identifier, unless ANSI_QUOTES mode is enabled.

Solution:
You can force the session to accept double quotes by adding the flag to your connection string or session variables:

SET SESSION sql_mode = 'ANSI_QUOTES';

(Or simply use backticks in your queries).

4. Default SQL Modes

To ensure data integrity and compliance with modern standards, our databases are deployed with the following strict SQL modes enabled by default:

ONLY_FULL_GROUP_BY
STRICT_TRANS_TABLES
NO_ZERO_IN_DATE
NO_ZERO_DATE
ERROR_FOR_DIVISION_BY_ZERO
NO_ENGINE_SUBSTITUTION

These settings prevent the database from accepting invalid data (like invalid dates or dividing by zero).