Azure

Tree Schema supports Azure databases MySQ & Postgres as well as SQL Server and all Azure SQL databases built on top of SQL Server.


Connecting in Azure

When connecting to Azure from within Tree Schema it is suggested to use the fully qualified username created within Azure. This applies to all database types. The format for this is:

  • <username>@<server>

For example, if your username is treeschemauser and the server is tsazureserver then you should user the username treeschemauser@tsazureserver. It is possible to connect to a public database without this fully qualified username, but all connections through a jump-server require this username format.

../../_images/azure_user_format.png

Note

SSL is currently only supported when directly connecting to a database in Azure.

Connecting to a Public Database

If your database has a public endpoint then you can connect directly from Tree Schema as long as the database server or your specific database have an inbound rule that allows access from Tree Schema.

The following firewall rule will allow Tree Schema direct access to a publicly exposed SQL database.

../../_images/azure_sql_firewall_rule.png

Connecting to a Private Database

When connecting to database that is denying public access you will need:

  1. A jump server (virtual machine) that does allow inbound SSH access from Tree Schema, here is an example of the inbound SSH access for Tree Schema (note - you can further limit the inbound access by specifying just your jump server IP address)

../../_images/azure_ssh_access.png
  1. A private endpoint created for the database that allows the jump server to access the database within the Azure network

../../_images/azure_deny_public_access.png

You will also need to add the jump server in Tree Schema and select it when setting up your database.

Note

Connections from Tree Schema to Azure through jump hosts can take a long time to establish (sometimes over 60 seconds). If you are certain your connection is setup properly but you receive a timeout error on the first request please try again. If the issue persists please contact us for help.