Choose and prepare the databases

Before you start

RC1 includes MySQL, PostgreSQL, and Microsoft SQL Server providers. Confirm the exact engine version and deployment family against your package's acceptance evidence.

A provider implementation is not a blanket support claim for Linux, Azure SQL Database, Azure SQL Managed Instance, or every server version.

Prepare three logical databases

1. Open first setup on the new Primary and select one provider.
2. Use separate Control, Workflow, and AI databases. All three must use the same provider.
3. Enter each database host, port, and logical name. The defaults are punaha_control, punaha_workflow, and punaha_ai.
4. Choose existing accounts or automatic provisioning. Review any replacement warning before confirming.
5. Use separate runtime and migration accounts with the minimum required rights.
6. Configure trusted TLS for remote connections and run every database test.
7. Continue only after all three tests pass.

Understand replacement and provider choice

Automatic provisioning may replace the exact named databases or their tables. Azure SQL Database resources must already exist. Never point a replacement operation at unrelated data.

The provider becomes fixed when setup commits it. An additional Node inherits that choice. Changing an environment value does not migrate an existing installation to another engine.

Check the result

Readiness reports the provider and the Control, Workflow, and AI dependencies. A Connection to an external database is separate from Product persistence support.

If validation fails

Check the selected server family, firewall, certificate identity, database existence, and account rights. Keep secrets out of logs and screenshots. Do not disable certificate verification to hide a remote TLS failure.

Next step

Continue to Finish first setup. Plan a coordinated backup and restore.