Getting Started with Microsoft Azure SQL Database
This getting started gives some clues to start working with Microsoft Azure SQL Database
In this page, you’ll learn to reverse your first Metadata, configure it to use Microsoft Azure Blob Storage, and produce Mappings or Processes using it.
A master key must exist in the target Microsoft Azure SQL Database.
This is required for Microsoft Azure SQL Database to access Microsoft Azure Blob Storage, which is used as a temporary place to load data for performances purposes.
Refer to Microsoft Azure Documentation to learn how to create a master key.
The first step is to create the Microsoft Azure SQL Database Metadata.
For this, simply create a new Metadata for the Microsoft Azure SQL Database as you would usually do for any other database.
You can refer to Connect to your Data page which explains the procedure.
The Microsoft MSSQL Server JDBC Driver must be used.
The complete JDBC URL of the Azure SQL Database must be used.
You can find it on the Azure portal.
Below, an example of configuration:
For performances purposes, Azure Blob Storage is used as temporary location to extract source data and then load it into Microsoft Azure SQL Database through BULK INSERT statement.
This offers better performances when loading large sets of data than using direct JDBC loading.
Therefore, Semarchy xDI Templates are using this method to have good performances.
This section explains how to configure Microsoft Azure SQL Database Metadata to work with an Azure Blob Storage container.
You can jump to next section if you prefer configuring this later.
The first step is to create an Azure Blob Storage Metadata and define a container for temporary files. You can refer to Getting Started with Microsoft Azure Blob Storage to do this.
Below, an example of an Azure Blob Storage Metadata:
|The container doesn’t have to exist on the storage, the Templates allow to create it automatically in case it doesn’t.|
Next step is to create the Link between the two Metadata.
To do this, drag and drop the Azure Blob Storage container from the Project Explorer in the SQL Database Metadata.
Depending on if you want to re-use it on several tables or schemas, drag and drop it on the desired node.
|In this example, we want it to be available for all tables so we put it on the schema.|
Finally, rename the Metadata link that is created to TARGET_AZURE_CONTAINER:
This is required as the Template will search for a Metadata Link named as this on the target Microsoft Azure SQL Database, to know where to store the temporary file.
Your Metadata being ready and your tables reversed, you can now start creating your first Mappings.
The Microsoft Azure SQL Database technology can be used like any other database in Semarchy xDI.
You can refer to Work with Mappings page which explains the procedure.
Loading data from a database into Microsoft Azure SQL Database
Loading data from a file into an Microsoft Azure SQL Database
The Microsoft Azure Component ships sample project(s) that contain various examples and use cases.
You can have a look at these projects to find samples and examples describing how to use it.
Refer to Install Components to learn how to import sample projects.