I found out that it took some trial to connect to a remote SQL Server-database, which is hosted in Microsoft's Azure cloud-environment, using the Enterprise Data Connector (EDC).
As Azure's SQL Server requires SSL to connect, finding the right connect-string required resulted in many errors. The EDC-documentation (up to version 5.4.1) unfortunately lacks any information about this. Thanks to [mention:621b0d77db5f4b6bbd4186ed76092592:e9ed411860ed4f2ba0265705b8793d05] and a little bit of tweaking, I got things working. It might help others in the future and spare some valuable time.
Enter the following in the Database Connection-pane, at the Database Access-tab of your vocabulairy (with Studio in Integration & Deployment-mode):
Database Server:
Microsoft SQL Server 2012
Database URL:
jdbc:progress:sqlserver://<address>.database.windows.net:1433;databaseName=<database_name>;encrypt=true;hostNameInCertificate=*.database.windows.net;loginTimeout=30;
Username:
username@<address>
At the additional properties-fields of the Database Access-tab, add the following values:
| Property Name | Property Value |
| EncryptionMethod | loginSSL |
| ValidateServerCertificate | true |
Please note that the hostNameInCertificate value starts with *. In some cases this might cause an error, where EDC will tell you what URL to use instead (for instance, data.am1-3.database.windows.net).
A Database Connection might look like this (with fictional database-URL):
Thanks for the information. SQL Azure is not a platform we have tested previously.