azure-docs
azure-docs copied to clipboard
Disconnect between options listed in overview and in details
There are the options listed in the Migrate section:
backup and restore minimal downtime migration by using backup and restore along with log shipping detach and attach from a URL convert to a VM ship a hard drive
The options detailed below are quite different. For example, Azure Data Studio is listed in details and not in the listing. Another example is that log shipping is only listed in the overview. This is very confusing. There should be correlation between TOC and detailed walkthroughs.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
- ID: 668f9bfd-5091-87b8-0d20-3beb6f9518a1
- Version Independent ID: 523ad222-50ee-a905-ddaf-1cc0d1602ace
- Content: SQL Server to SQL Server on Azure Virtual Machines: Migration guide - SQL Server on Azure VMs
- Content Source: azure-sql/migration-guides/virtual-machines/sql-server-to-sql-on-azure-vm-individual-databases-guide.md
- Service: virtual-machines-sql
- Sub-service: migration-guide
- GitHub Login: @markjones-msft
- Microsoft Alias: markjon
@VitalyMCT Thanks for your feedback! We will investigate and update as appropriate.
@VitalyMCT Thanks for bringing this to our attention. I'm going to assign this to the document author so they can take a look at it accordingly.
@markjones-msft Could you please add your inputs on above query
Hi @VitalyMCT , thanks for contacting Microsoft! Our apologies for the delay in response, as we're working through a large backlog of items. The changes you're proposed are good, and we're going to bundle them in with a few other refresh changes to this article. As such, we're going to move tracking this item to our internal system and close out this Git Issue. However, please feel free to comment should you need anything further.
Thanks again for reaching out and I hope you have a wonderful rest of your day! Masha from the SQL Docs team #reassign:rwestMSFT #please-close
@VitalyMCT Adding to my colleague's comments: if you would like to open a pull request in the meantime, please do so, and we can review the change a lot quicker.
@VitalyMCT I have created an internal pull request for this article, which addresses the issues you've provided. When it is approved, you can expect to see the updated article in the next few days. Thank you again for your feedback.