Scribd
Upload
316 views9 pages

Migration On-Premise Database To Azure Database: Some of The Migration Tools

The document discusses various tools and methods for migrating an on-premise database to Azure SQL Database, including the Migration Assistant tool, Migration Assistant service, backups, manual scripting, and replication. It also covers Azure database models like IAAS, PAAS, and SAAS, and discusses options for high availability and disaster recovery using features like active geo-replication and auto-failover groups.

Uploaded by

lavanya ya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
316 views9 pages

Migration On-Premise Database To Azure Database: Some of The Migration Tools

The document discusses various tools and methods for migrating an on-premise database to Azure SQL Database, including the Migration Assistant tool, Migration Assistant service, backups, manual scripting, and replication. It also covers Azure database models like IAAS, PAAS, and SAAS, and discusses options for high availability and disaster recovery using features like active geo-replication and auto-failover groups.

Uploaded by

lavanya ya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 9

Migration On-premise Database to Azure Database

Some of the migration Tools:


1. Migration assistant tool (offline)
https://www.microsoft.com/en-us/download/details.aspx?id=53595
2. Migration assistant service (offline + online) (full load +incremental load)
3. Backup(backpack) (testing need to be done prior)
4. Manual (script generate+ Data (import/export or linked server)
5. Replication (online)

1.Migration Assistant Tool:


 Application downtime required
 Easy to migrate complex databases
 Assessment, we can do before migration
 From SQL Server to ALL DTU Models DB’s, we can migrate. Below is the Image
2.Migration assistant service (offline + online {full load +incremental load} )
 Best Choice is Migration Assistant Service
 No downtime for the application
 Non- SQL Server to Azure SQL
3.Backup(backpack) (testing need to be done prior)
 Easy to migrate
 Make sure thoroughly tested with zero errors
 While migration, complete deployment will fail, if any object does not support in
azure

-------------------------------------------------------------------------------------------------------------------------------

AZURE DATA Models


1. IAAS Model
2. PAAS Model
3. SAAS Model

1.IAAS Model:
 Will get Windows from Azure
 You can start/stop Services
 Same as like On-premise

2.PAAS Model:
Pass model again 3 Types:

a. Single database model


b. Elastic pool database model
c. Managed instance

Below are pass model Properties

Single database model & Elastic pool database model & Managed Instance
 No windows login
 You can’t start/stop sql service
 SQL Server name will be like xxxxxxxxxxxx.database.windows.net

Single database model & Elastic pool database model


 Cross queries are not possible by default
 Only Master database and No Model, Msdb, Tempdb databases
 No SQL AGENT
 No Linked server
 No Database Mail
 You can’t take the Manual backups
 You can’t restore the Databases
 No Server level Roles only database level roles
 There are two extra db level roles for the Master database called DBManager and
LoginManager roles
 For the Master DB, you cannot assign any other roles not even DB_DataReader
 You can create any objects (except login and user) in Master database
 You can’t change the recovery model of the Database
 DTU Model & Vcore Model support
 You cannot make single user/offline mode but you can rename the databases

Single database model


 Each database has its own compute (Own hardware)

Elastic Pool database model


 Common hardware pool shared by databases
 Different time and different database load is different, you can use this model to save
the DTU cost
Managed instance
 Almost 100% equal to the On-premise Server
 Cross queries are possible
 Native backups possible
 Master, Model, Msdb and Tempdb available
 DB Mail available
 Linked Sever available
 SQL AGENT available
 For additional details on this Managed Database properties, you can see on
“Azure_SQL_Database_Managed_Instance_Technical_overview.pdf” file

-------------------------------------------------------------------------------------------------------------------------------
Compute + storage options in PASS Model
1. DTU Model
2. Vcore Model
DTU or eDTU model again 3 Types

a. Basic
b. Standard
c. Premium  

VCore model again 3 Types

a. General Purpose
b. Hyperscale
c. Business Critical

DTU Model: Data Transaction Unit


 Blend of CPU, Memory and IO (like 1+ 1 offer 😊 )
 You can use DTU Calculator for- How many DTU’s required for on-premise database before
migrating the database into Azure
 You can also decide- how many DTU’s are really required for Azure DB based on its usage graph.

VCore Model:
 Independent scaling IO, CPU and Memory

Choosing DTU or Vcore?


Security in Azure DB:
 No Server level Roles
 Only DB level roles are there
 Extra two roles dbmanager & loginmanager
 These extra roles for only Master DB

SQL Authentication:
CREATE USER Raj for login Raj (before should create login)
CREATE USER [Raj] WITH PASSWORD = 'Welcome@1234' (without login)

Azure Active Directory - Universal with MFA: (like windows Authentication in On-
premise)
CREATE USER [[email protected]] FROM EXTERNAL PROVIDER
CREATE USER [DBAdmins] FROM EXTERNAL PROVIDER

exec sp_addrolemember 'db_owner',[DBAdmins]


exec sp_addrolemember 'db_datareader',[DBAdmins]
exec sp_addrolemember 'dbmanager',[DBAdmins]
exec sp_addrolemember 'loginmanager',[DBAdmins]

Master db Only
dbmanager and loginmanager and no other roles

Userdb's:
Same db roles like onpremise
-------------------------------------------------------------------------------------------------------------------------------

HA & DR
Azure SQL Database provides Active Geo-Replication and Auto-Failover groups for disaster recovery
and High Availability
Azure SQL Database Active Geo-replication
 Uses AlwaysOn to asynchronously replicate data from primary to secondary databases.
 Supports four readable secondary’s in the same or different Azure regions. Secondary’s can
also be used to offload read-only workloads other than disaster recovery.
 Allows primary and secondary databases to be in different service tier if required. You can
switch to a lower service tier for secondary database to save cost, however, if you failover
to secondary, you won’t get the performance of the primary database.
 Supports Manual failover. After a successful failover, all other secondary’s automatically
point to the new primary.
 Supports failover of an individual or set of databases from Primary to Secondary, even the
databases in an elastic pool are also supported
 Is available for all service tiers.

Below is the step by step document for creation of GEO Replication and Failover group

Geo Replication Step By step.docx

Geo Replication
Step By step.pdf

Thanks,

Rajasekhar Reddy Bolla

Microsoft Certified SQL Server DBA/ Azure DBA/ Architect 

+91-9966246368

[email protected]

(contact for Azure SQL Trainings and Videos and Realtime Issues)

You might also like