9 and 10 experiment

You might also like

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 20

EXPERIMENT: 9

Experiment 9:- Create a logical server in Azure and a Hyperscale database in


Azure SQL Database using the Azure portal.

Student Name: Shruti Jha


UID:22/FCA/BCA(DS&BDA)/024

1. Aim/Overview of the practical:


To deploy a logical server in Azure and create a Hyperscale database in Azure
SQL Database using the Azure portal.

2. Task to be done:-
Create and deploy a logical server in azure portal.

3. Observations:-
Observer the scalability options provided by the Hyperscale architecture, such as
scaling compute and storage independently.

4. Results:-
Here the result is that we will be able to successfully deploy a logical server in
Azure and create a Hyperscale database. Additionally, we would have a clear
understanding of the configuration options available for scaling and managing
databases in Azure SQL Database.

5. Learning outcomes:-
We will be able to Understand Azure's infrastructure for deploying databases and
become familiar with the process of creating a logical server and Hyperscale
database in Azure SQL Database.
Here are the steps and pictures related to the experiment.

Step 1- Sign in to the Azure portal.

Step 2- On the Azure portal menu or from the Home page, select Create a
resource. The Create a resource pane appears. Search for SQL database server.
Step 3- You will be navigated to another webpage. Click on SQL server (logical
server).

Step 4- A new webpage will appear. Click on create.


Step 5- Enter the following values on the Create SQL Database page, and
leave all other properties with their default setting:

Subscription- Choose your subscription.


Resource Group- Create a new resource group or select an existing one.
Logical Server Name- Enter a name for your logical server.
Region- Choose the region where you want to deploy your logical server.
Server- Enter a unique server name.
Authentication- Create an administrator login and password.
Step 6- Click on networking tab. Select yes to allow azure services and resources.

Step 7- Go to Review+create tab and click create.


Step 8- After we click on create, the deployment of logical server will start.

Step 9- After the deployment is completed, we will get a New Azure SQL
Database logical server.
Step 10- Download the adventure work .bak file for database. Store .bak files
inside the Backup directory of your SQL Server. Search your local SQL server
installation directory and locate the Backup directory, which is usually C:\Program
Files\Microsoft SQL Server\MSSQL.SQLEXPRESS\MSSQL\Backup. Paste the
files inside the mentioned directory.

Step 11- Connect to your local SQL Server. Open SSMS and access the database
engine with the default Windows authentication and click Connect.
Step 12- Select the Databases node, right click and click on Restore Database.

Step 13- The Restore Database window will appear on the screen. On
the General page, use the Source section to specify the source and location of
the backup set to be restored. Now, select the Device option and click the Browse
(...) button.
Step 14- This will open the Select backup devices dialog, here you will be able
to select the .bak files from the directory mentioned on the first step when you
click on Add.

Step 15- Locate and select the SQL database backup file(s) (.bak) that you want
to restore, and click the OK button to proceed.
Step 16- This will add the files to the backup devices, and click on OK.

Step 17- In the Destination section, the Databases box is automatically populated
with the name of the database to be restored. Now, you need to rename the
destination database, to do so enter the new name in the Database box. And, leave
the default values as it is in the "Restore to" box and "Backup sets to restore"
grid.
EXPERIMENT: 10
Experiment 10:- Install the Azure SQL Migration extension for Azure Data Studio.
a.Migrate SQL Server to Azure SQL Database(offline)
b.Migrate SQL Server Azure SQL Managed Instance online in Azure Data Studio
Migrate SQL Server to Azure SQL Managed Instance offline in Azure Data Studio

Student Name: Shruti Jha


UID: 22/FCA/BCA(DS&BDA)/024
1. Aim/Overview of the practical:
To install the Azure SQL Migration extension for Azure Data Studio and perform
migrations from SQL Server to Azure SQL Database and Azure managed
instance both online and offline.

2. Task to be done:-
Install the Azure SQL Migration extension for Azure Data Studio, migrate SQL
server to Azure SQL database(offline) and Azure SQL managed instance in Azure
data studio.

3. Observations:-
Observed installation of the Azure SQL migration extension for Azure Data studio.

4. Results:-
Here the result is that the Azure SQL Migration extension was installed
successfully.

5. Learning outcomes:-
We will be able to Understand the process and steps involved in installing the
Azure SQL Migration extension for Azure Data Studio.
Here are the steps and pictures related to the experiment.

Step 1- Open the extensions manager in Azure Data Studio. You can either select
the extensions icon or select Extension in the View menu.

Step 2- Type Azure SQL Migration in the search bar. Select the Azure SQL
Migration extension and view its details. Select Install.
Step 3- You can see the Azure SQL migration extension in the extension list once
installed.

Step 4- You can connect to the SQL server instance in Azure Data Studio. Right-
click the instance name and select Manage to see the dashboard and the Azure
SQL Migration extension landing page.

Step 5- Once connected a new server overview tab will appear. Choose Azure
SQL Migration under the General heading.
Step 6- This will launch the Azure SQL Migration blade. Choose one of the two
"Migrate to Azure SQL" buttons on the Azure SQL Migration blade to start the
migration wizard.

Step 7- Choose the Azure account under which the migration will run. You can
link an Azure account in this step or choose from an existing account linked in
Azure Data Studio.
Step 8- Choose the database or databases to migrate.

Step 9- Select the Azure SQL target. For this migration we will choose Azure SQL
Managed Instance. Choose the "View/Select" button to review the assessment
results.
Step 10- Select either an online or offline migration mode.

Step 11- Specify the location of the database backups. You can either use a local
network share (SMB) or an Azure Storage Blob Container.
Step 12- When network share is selected, the wizard will prompt you for a few
additional details.

Source Credentials: The specified account must have a minimum of


CONTROL SERVER permissions to identify valid database backup files.
Network share details: Specify the network location (SMB) where the
database backup files are located. This is the location that the self-hosted
integration runtime will periodically check for new database backups.

Step 13- Select the Resource Group containing the Azure Database Migration
Service as well as the Azure Database Migration Service itself.
Step 14- Migration wizard will provide a summary of the migration. Choose
"Done" in the lower right corner to begin the migration. A pop-up will appear in
the lower right corner of Azure Data Studio indicating that the migration has
started.

Step 15- The Database Migration Status section of the Azure SQL Migration tab
will also indicate the number of migrations that are in progress. Choose "Database
migration in progress" to view migration details on the Migration Status.

Step 16- The Migration Status screen will contain one entry per migrated database.
Choose a database from the list to view detailed migration status information.
Step 17- When you are ready to complete the migration and cutover to Azure SQL
Managed Instance, choose "Complete cutover". The "Complete cutover" blade
will appear from the right side of the screen asking for verification that no
additional transaction log backups should be restored before cutover. Select the
confirmation checkbox and choose "Complete cutover" button.

Step 18- Once cutover is completed, the Migration Status will indicate
"Succeeded". The Database Migration Status section on the Azure SQL Migration
screen will also update accordingly.

You might also like