Migrating to Azure SQL Database with Always Encrypted
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start with the migration process described in the data-migration-sql README and the linked Data Migration Service Always Encrypted FAQ. Determine the required migration workflow and how Always Encrypted with Secure Enclaves should be covered; done means an agreed process that supports encrypted columns in Azure SQL Database.
Written by the indexing model from the issue text.
Description
Please provide us with the following information:
This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
Minimal steps to reproduce
Currently, if you're migrating from an on-prem database with encrypted columns to an Azure SQL Database, the Data Migration Service does not support Always Encrypted columns, even though Azure SQL Databases support Always Encrypted
Any log messages given by the failure
https://learn.microsoft.com/en-us/azure/dms/faq#always-encrypted
Expected/desired behavior
A process is defined to be able to migrate databases with encrypted columns to Azure SQL Databases using similar processes to the "Migrate Databases at Scale Using Azure Data Migration Automation" process.
OS and Version?
Windows
Versions
Mention any other details that might be useful
Always Encrypted with Secure Enclaves support would be helpful to have as well. Always encrypted is a very common practice nowadays to protect sensitive information and PII. It would be great if the Data Migration Service was able to support migrating Always Encrypted enabled databases the same way it supports all other databases.
Thanks! We'll be in touch soon.
- Dominant language
- PowerShell
- Stars
- 24
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure-Samples/data-migration-sql
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Azure-Samples/data-migration-sql#9 · 1 comment ·
-
Support "Active Directory Password" authentication method for TargetSqlConnectionAuthentication Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure-Samples/data-migration-sql#8 · 1 comment ·
All issues in Azure-Samples/data-migration-sql
Similar issues
-
Product: Azure Policy :shield: Topic: Diagnostic Settings :test_tube: Topic: Policy :pencil:
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
Azure/Azure-Landing-Zones#4283 · 1 comment ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug zenodo
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Language: Terraform :globe_with_meridians: Needs: Triage :mag: Type: Bug :bug:
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Azure/terraform-azurerm-avm-res-containerregistry-registry#230 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100