Introduction
A database copy is a transactionally constant snapshot of the supply database taken at a particular second in time after the copy request has been despatched. For the copy, you should utilize the identical or a distinct server. You can too protect the supply database’s backup redundancy, service tier, and compute measurement, or change the backup storage redundancy and/or compute measurement inside the identical or one other service tier. It turns into a totally useful, self-contained database after the copy is completed. The replicated database’s logins, customers, and permissions are managed individually from the supply database.
Logins within the database copy
The identical logins can be utilized on each databases whenever you replicate a database to the identical server. On the brand new database, the safety principal you used to duplicate the database turns into the database proprietor.
Whenever you copy a database to a brand new server, the safety principal who began the copy course of on the goal server turns into the brand new database’s proprietor.
To handle database copies, use Azure RBAC roles and permissions.
To create a database copy, you will have to be within the following roles
- Subscription Proprietor or
- SQL Server Contributor function or
Customized function on the supply and goal databases with following permission,
Microsoft.Sql/servers/databases/learn Microsoft.Sql/servers/databases/write
To cancel a database copy, you will have to be within the following roles,
- Subscription Proprietor or
- SQL Server Contributor function or
Customized function on the supply and goal databases with following permission,
Microsoft.Sql/servers/databases/learn Microsoft.Sql/servers/databases/write
To handle database copy utilizing the Azure portal, additionally, you will want the next permissions,
Microsoft.Sources/subscriptions/sources/learn Microsoft.Sources/subscriptions/sources/write Microsoft.Sources/deployments/learn Microsoft.Sources/deployments/write
Microsoft.Sources/deployments/operationstatuses/learn
If you wish to see the operations beneath deployments within the useful resource group on the portal, operations throughout a number of useful resource suppliers together with SQL operations, you will have these further permissions:
Microsoft.Sources/subscriptions/resourcegroups/deployments/operations/learn
Microsoft.Sources/subscriptions/resourcegroups/deployments/operationstatuses/learn
We have already got an Azure SQL Database, however we’d like an actual reproduction of it.
On this case, I will display how the duty is accomplished.
Step 1
To repeat a database through the use of the Azure portal – Navigate to SQL Database,
Step 2
Choose the SQL Database – Click on Copy
Step 3
Choose the Database Identify
Choose the Database Server
Choose Backup Storage Redundancy
Evaluate + Create
The permissions of all customers within the new database are the identical as they have been within the previous database. The database proprietor of the brand new database is the consumer who initiated the database copy. Solely the database proprietor can log in to the brand new database after the copying is full and earlier than different customers are remapped.
Abstract
We realized copy a transactionally constant copy of a database in Azure SQL Database on this tutorial. Please depart a remark within the remark field when you’ve got any questions.
