Database Reference
In-Depth Information
However, in order to interact with the cloud services of Azure, and work with Azure ser-
vices locally, the Azure SDK has to be installed into the local machine mentioned earlier.
For storage service's data management, we can create a SQL database in the cloud, and
use a SQL database on-premise from the cloud, or a hybrid thereof. The main difference is
that the connection string in the SQL Server database points towards an on-premise or off-
premise server. A virtual network can be set up between the cloud and an on-premise
LAN to provide a secure network connection. When connecting to SQL Servers, IPs have
to be explicitly allowed through the firewall to the cloud database. There is a lot of built-
in security to protect the cloud services. The Azure SDK interfaces through Visual Studio
so that there are tools to build SQL tables, stored procedures, and more, from Visual Stu-
dio to the Azure cloud SQL database.
We can even manage the SQL database in the Azure Cloud from SQL Management Stu-
dio.
This, in turn, means that we can use it to create entity models, and use the remote SQL
database for NServiceBus persistence as we would in a local SQL database, and any other
coding that we would do in a local SQL database. The only difference is that it is living in
the Azure cloud. Here, we are developing entities from the cloud database.
