Wednesday, 16 May 2018

Takeaway notes from Azure session on Azure SQL databases

How many SQL instances get created based on your Azure subscription? 

Below is the Component which gets created as per your PAAS Subscription.

For E.g I have created the XP0 single instance and we got the below instance. I have masked the data as usual.

How can I allow my IP or IP ranges in order to connect to Azure sql Database?

Choose your sql database and goto  Firewalls and virtual networks and add your IP ranges as shown below.

How can I change the Resource Configuration & Pricing for given Database?

By Default, as highlighted above all the databases are created as "Standard" Option by means of resource Configuration & Pricing.

Choosing a service tier depends primarily on business continuity, storage, and performance requirements.

considering the retention period, we choose basic for CORE database while resting on a standard 

What you mean by DTU?

DTU Stands for Database Throughput Unit (DTU) and it represents a blended measure of CPU, memory, reads, and writes

In the DTU-based purchasing model, customers can choose between Basic, Standard, and Premium service tiers for both single databases and elastic pools.

What you mean by Elastic pool ?

SQL Database elastic pools are a simple, cost-effective solution for managing and scaling multiple databases that have varying and unpredictable usage demands. The databases in an elastic pool are on a single Azure SQL Database server and share a set number of resources at a set price

  • Its cost-effective model
  • No need of over provision
  • No need to worry about individual performance.
  • Individual databases can be configured

Keep Analytics database separate and rest of the database in one elastic pool.

The steps are very simple:
-Create 1 Azure Sql Server
-Create 4 Azure Sql Databases (and import associated Sitecore databases).

-Create 1 Azure Sql Elastic Pool
-Add to pool the 4 Azure Sql Databases

Monday, 14 May 2018

Takeaway notes from Azure session on Deployment Slots

Q: What is Deployment slot?

Image result for Deployment slots

A deployment slot is an additional Azure App Service Web App instance (W3WP) which is ~bound to your production Azure App Service Web App of the same name and runs on the same App Service Plan.

Deployment slots are also known as staged deployment.

A deployment slot will carry the name of the Azure Web App + the name of the slot.
For e.g  If my Azure Web App is called mysite and I create a slot called staging then its url will be

By default, each Azure Web App has a single deployment slot called production which is the Azure Web App itself.

Please note slot is in itself a regular Azure Web App.

Q: Why Deployment slot?

  1. The development slot helps you to test your code prior to the release of the live Web App.
  2. with just a click the new version is live as deployment slot is swapped with the production
  3. Staged Deployment
  4. Autoswap
  5. A/B testing can be executed using different slots

Q: How many deployment slots?

By default, each Azure Web App has a single deployment slot called production which is the Azure Web App itself.

You can add more than one slot as per your business needs.

Q:  How the configuration works between slots.

By default, App Settings and database connection strings are NOT sticky to the slot and will follow the Web App when the test slot is swapped with the production slot.

We need to make the setting sticky to slots so it does not get swapped.

Image result for Deployment slots