You should create a distributed network name (DNN) resource 1. On Azure Virtual Machines, the DNN routes traffic to the appropriate clustered resource. It provides an easier way to connect to the SQL Server failover cluster instance (FCI) than the virtual network name (VNN), without the need for an Azure Load Balancer 1.

View or change the compatibility level of a database
You can view or change the compatibility level of a database in SQL Server, Azure SQL Database, or Azure SQL Managed Instance by using SQL Server Management Studio or Transact-SQL.
Use SQL Server Management Studio
To view or change the compatibility level of a database using SQL Server Management Studio (SSMS) Step 1: Connect to the appropriate server or instance hosting your database [Here db1].
Step 2: Select the server name in Object Explorer.
Step 3: Expand Databases, and, depending on the database, either select a user database or expand System Databases and select a system database.
Step 4: Right-click the database, and then select Properties.
The Database Properties dialog box opens.
Step 5: In the Select a page pane, select Options.
The current compatibility level is displayed in the Compatibility level list box.
Step 6: To change the compatibility level, select a different option from the list [Select SQL Server
2012]
Reference:
https://learn.microsoft.com/en-us/sql/relational-databases/databases/view-or-change-the-compatibility-level-of-a-database

Explanation:
Follow these same steps to create striped virtual disk:
- Create Log Storage Pool.
- Create Virtual Disk
- Create Volume
Box 1: a storage pool
Box 2: a virtual disk that uses the simple layout
There are only three layouts while creating virtual disks on a storage pool:
Simple - Data is striped across physical disks, maximizing capacity and throughput Mirror - Data is striped across physical disks, creating two or three copies of data Parity - Data and parity information is striped across physical disks, increasing reliability Box 3: a volume Reference:
https://hanu.com/hanu-how-to-striping-of-disks-for-azure-sql-server/

When you migrate databases to Azure by using Azure Database Migration Service, you can do an offline or an online migration. With an offline migration, application downtime starts when the migration starts. With an online migration, downtime is limited to the time to cut over at the end of migration. We suggest that you test an offline migration to determine whether the downtime is acceptable; if not, do an online migration.
Reference:
https://docs.microsoft.com/en-us/azure/dms/tutorial-sql-server-to-managed-instance

Explanation:
Use the following steps for column level encryption:
1. Create a database master key (Step 1)
2. Create a self-signed certificate for SQL Server (Step 2)
3. Configure a symmetric key for encryption (Step 3)
4. Encrypt the column data (this includes Open the symmetric key - Step 4)
5. Query and verify the encryption
Step 1: Create a database master key
Create a database master key for column level SQL Server encryption
In this first step, we define a database master key and provide a password to protect it. It is a symmetric key for protecting the private keys and asymmetric keys.
Step 2: Create a certificate.
Create a self-signed certificate for Column level SQL Server encryption In this step, we create a self-signed certificate using the CREATE CERTIFICATE statement. You might have seen that an organization receives a certificate from a certification authority and incorporates into their infrastructures. In SQL Server, we can use a self-signed certificate without using a certification authority certificate.
Step 3: Create a symmetric key.
Configure a symmetric key for column level SQL Server encryption.
In this step, we will define a symmetric key that you can see in the encryption hierarchy as well.
The symmetric key uses a single key for encryption and decryption as well.
Step 4: Open the symmetric key
Data encryption.
Let's encrypt the data in this newly added column.
In a query window, open the symmetric key and decrypt using the certificate. We need to use the same symmetric key and certificate name that we created earlier Etc.
Reference:
https://www.sqlshack.com/an-overview-of-the-column-level-sql-server-encryption/