How to create Azure SQL Database logical server?

To create a Azure SQL database we first need to have a Azure SQL Database logical server. We can create this logical server during creation of Azure SQL database or separately.

 

In this article we will see how to create a Azure SQL Database logical server which is prerequisite for creating Azure SQL database.

 

Login to Azure portal “portal.azure.com” and search for “Azure SQL”. Select "Azure SQL" and 

 

then click on ‘Create’ in the page opened

 

It will take us to new page which will have options to create all the different Azure SQL resources. Here under “SQL databases” section in the “Resource type” select “Database Server” 

 

and click “Create”

It will take us to the “Basics” tab of “Create SQL Database Server” page. Here fill the details of

 

Subscription : Your subscription

Resource group : The resource group where you want the resource to be created

Server name : You can give name of your choice

Location : Where the Azure DB server should be created

 

I am giving my DB server name as “azurelss” and location selected "Central India"

 

 

in next section select “Authentication method” as “Use both SQL and Microsoft Entra authentication” this will allow us to have two sysadmins for the DB server, one is AD account and other is SQL login.

Click on “Set admin” in “Set Microsoft Entra admin” and here you can select the required AD account and I’m selecting a email account.

 

Next give the “Server admin login” as “sqladmin” (you can give as per your choice) and give password for it in “Password” section.

 

 

Then click on “Next: Networking” which takes to next tab which is “Networking” leave all the values as it is in this page, we can configure the firewall rules for this server later.

Similarly leave all other tabs like Security, Additional settings, Tags with default values and once you reach “Review + create” click on “Create” and it will start creating the DB server.

 

If you notice the DB server is Free and there won’t be any charges for it.

 

You can see DB server creation in progress and after sometime it will complete.

 

Once you click on “Go to Resource” it will take you to the Azure DB server and here you can verify all the DB server details which we created.

 

Here in the "Server Name" section we can see our Azure Database Server FULL name. In our case it is "azurelss.database.windows.net"

In the next article we will see how to create a Azure SQL database.

 

Thanks VV!!

Azure Devops Pipelines Basics

In this article we will see what are the different components of Azure Devops Pipelines.

These components are there basic foundation of Azure Devops Pipelines, understanding these plays a key role while working on Azure Devops.

Trigger : As the name suggests it will start the Pipeline execution. Trigger can start a pipeline as per schedule or if any activity happens. In short, when the pipeline should run is defined in a trigger.

Stages : It is the logical separation between different environments like we can a stage for Dev environment, one for QA and so on. A pipeline can have single or multiple stages. By default the stages will run one after another, we can also specify conditions when a stage to run.

Job : A job is collection of single or multiple steps. It is the smallest unit in a pipeline which can be scheduled. Each Stage in a Azure Pipeline will have single or multiple Jobs. Every pipeline will have at least one job.

Job Agent : To build or deploy code we need at least one job agent. Job agent acts as a compute infrastructure for the jobs to run. Note: Few jobs can run without agent also.

Step : Step is the smallest building block of a Azure Pipeline. Each job step will have details of the actual action that needs to be done. Each job will have single or multiple Steps.

Task : A task can be a script or procedure to perform certain action. Action can be building an application, deploy IoT image, push docket images and so on. There are many built-In tasks and custom tasks can be created as well.

#AzureDevOps #AzurePipelines

Azure Devops Common mistakes - 1

One of the most common mistakes people commit in Azure Devops is not having identical Development, Test and Production environments.

The better way to address this is to use infrastructure as code (IaC) tools like Azure Resource Manager (ARM) templates or Bicep to define your infrastructure in a consistent and repeatable way.

This will ensure that all environments are identical, regardless of who created them.

#azuredevops #azurearchitect