This article describes how DataGalaxy Azure SQL connector works.
This connector is available in the following modes:
| Desktop mode ✅ | SaaS Online mode ✅ |
|---|
This connector supports the following import modes:
| Standard mode ✅ | URN mode ✅ |
|---|
- Connector scope
- Configuration of a connection
- Execution of the connector
Connector scope
The connector allows you to import the following metadata from Azure SQL into a Database source:
- The set of schemas for a given database
- The content of the schemas: tables, views and columns
- Primary and foreign keys between tables
The extracted objects and their correspondences are detailed in the following table:
| Azure SQL Object | DataGalaxy Object | Comments |
|---|---|---|
| Schema | Model (Container) | |
| Table | Table (Structure) | Comments are uploaded to the DataGalaxy Technical Comment field. |
| View | View (Structure) | Comments are uploaded to the DataGalaxy Technical Comment field. |
| Column | Column (Field) | Name, data type (size and precision), description, order are returned when available. Comments are uploaded to the DataGalaxy Technical Comment field. |
| Primary Key | Primarey Key | This information will be used to link tables in DataGalaxy diagrams |
| Foreign Key | Foreign Key |
Configuration of a connection
Azure SQL connector uses the JDBC driver provided by Microsoft.
The following information is required to set up a connection:
| Parameter | Mandatory | Description |
|---|---|---|
| Server | Yes | Azure SQL Server name |
| Port | Yes | Azure SQL Server port |
| Database | Yes | Limits the scope to the specified database |
| Schema | No | Limits the scope to the specified schema |
| Available authentication modes: | ||
| SQL/AAD password (desktop)/ AAD password with MFA (desktop) | ||
| User | Yes | |
| Password | Yes | |
| AAD Service principal (desktop) | ||
| Tenant ID | Yes | Tenant ID |
| Client ID | Yes | Client ID |
| Client Secret | Yes | Client secret |
| Advanced mode | ||
| Advanced mode (Desktop connector option) | No | Option to customize the JDBC URL used to connect |
Execution of the connector
To create a connection to Azure SQL via the Online connector, the entry points are as follows:
- From the Import button of the "Shortcuts" widget on the home screen of a client space or workspace
- From the Import button of one of the modules when it is empty
- From the Import button in the contextual menu of one of the modules, on the right side of the filtered views
- From the Add a connection button in the Connector tab available in the workspace setup screen
You can optionally filter (by module, connector type or by using the search bar), then click on the desired technology:
You then need to complete the login form using the login information described above to perform an import. For more details on the steps involved in running the Online connector, you can consult the following article: [HowTo] Running the Online Connector.
This technology is also available via the Desktop Connector, you can find more information on the procedure here: [How to] How to use the connector.
Releases
| Date | Version | DataGalaxy Version | Desktop Connector version (minimum) | Description |
|---|---|---|---|---|
| 29/09/2026 | 7.1.2 | 3.423.0 | 6.2.2 | New internal implementation to fix security vulnerabilities |
| 16/07/2026 | 6.1.0 | v3.379.0 | 5.18.5 | Retrieval of stored procedure now supported in URN mode |
| 23/06/2026 | 5.0.10 | v3.360.0 | 5.16.1 | Fixed some security vulnerabilities |
| 23/01/2026 | 5.0.5 | v3.302.1 | 5.15.4 | Orphaned handling feature bugfix for urn mode |
| 31/12/2025 | 5.0.4 | v3.295.4 | 5.15.4 | Orphaned handling feature bugfix for urn mode |
| 02/07/2024 | 4.0.0 | 3.55.0 | 5.0.1 | Migrated from java 11 to java 17 + CVE fixes |
| 12/03/2024 | 3.3.1 | 3.34.1 | Addition of extra authentication options (desktop) |