In the “Databases” screen on Invantive Cloud, three links are now visible to connect externally to a cloud database:

The first two links are for use with Power BI, Qlik, and Tableau. The third and new link is the name to use when connecting based on the SQL Server network protocol. In the above example, it is:
acme-exact-online.database.invantive.com
Logging in from SQL Server Programs
When logging in via SQL Server, enter this name under “Server name” as shown in this example for SQL Server Management Studio:

You can choose “Mandatory” or “Optional” under “Encryption”. The server certificate of the Invantive database server is automatically checked. You can leave “Trust server certificate” unchecked.
SQL Server Management Studio
After logging in from SQL Server Management Studio, much functionality is available:

The service providers of an Invantive UniversalSQL database can be found under “System Databases”. All other providers (such as the online ECB exchange rates in the example above) appear as regular databases in the list. Items such as column names are also easy to expand.
Note that a red squiggly line appears under the table name of the ECB table. SQL Server Management Studio tries to interpret statements according to SQL Server syntax to signal typos early. However, Invantive UniversalSQL has notations that SQL Server does not recognise. Therefore, it is not unusual for parts to be underlined in red.
Procedures and functions for use in the procedural extension of Invantive UniversalSQL can be found under “Stored Procedures”, such as this one for deleting Group ID Access Requests on GitLab:

The list of stored procedures can be empty or very long, depending on what the respective Cloud package offers.
Views
Views are also accessible from SQL Server products, such as here the branches of a GitLab user:

Sumatra
For Sumatra, the use of Sumatra caches is recommended.
Microsoft Power BI and Microsoft Excel Power Query
Currently, a bug still prevents retrieving columns with Power BI and Power Query.
List of Available Databases
As elsewhere in Invantive products, entering an incorrect name leads to a suggestion of what the correct name should be, limited to a maximum number of, for example, eight. In the case of SQL Server:

itgentsr100 > The selected database segment ‘wrongname’ must exist for party ‘…’. > Please verify that a database with this segment exists for the party. > Or choose another database from: …