Merge pull request #229868 from rwestMSFT/rw-0308-dms-update-metadata

[BULK] Change owner and update metadata for DMS articles

Author: PMEds28

articles/dms/faq.yml

@@ -5,7 +5,6 @@ metadata:
   services: database-migration
   author: croblesm
   ms.author: roblescarlos
-  manager: craigg
   ms.reviewer: craigg
   ms.service: dms
   ms.workload: data-services

articles/dms/includes/sql-database-limitations.md

@@ -1,9 +1,9 @@
 ---
-author: MashaMSFT
+author: croblesm
+ms.author: roblescarlos
+ms.date: 01/25/2023
 ms.service: dms
 ms.topic: include
-ms.date: 01/25/2023
-ms.author: mathoma
 ---
 
 Azure SQL Database offline migration utilizes Azure Data Factory (ADF) pipelines for data movement and thus abides by ADF limitations. A corresponding ADF is created when a database migration service is also created. Thus factory limits apply per service.
@@ -17,4 +17,4 @@ Azure SQL Database offline migration utilizes Azure Data Factory (ADF) pipelines
 - Tables with large blob columns may fail to migrate due to timeout.
 - Database names with SQL Server reserved are currently not supported.
 - Database names that include semicolons are currently not supported.
-- Computed columns do not get migrated.
+- Computed columns do not get migrated.

articles/dms/includes/sql-managed-instance-limitations.md

@@ -1,9 +1,9 @@
 ---
-author: MashaMSFT
+author: croblesm
+ms.author: roblescarlos
+ms.date: 12/19/2022
 ms.service: dms
 ms.topic: include
-ms.date: 12/19/2022
-ms.author: mathoma
 ---
 
 - If migrating a single database, the database backups must be placed in a flat-file structure inside a database folder (including the container root folder), and the folders can't be nested, as it's not supported.
@@ -16,4 +16,4 @@ ms.author: mathoma
    - SSIS packages
    - Server audit
 - You can't use an existing self-hosted integration runtime created from Azure Data Factory for database migrations with DMS. Initially, the self-hosted integration runtime should be created using the Azure SQL migration extension in Azure Data Studio and can be reused for further database migrations.
-- A single LRS job (created by DMS) can run for a maximum of 30 days. When this period expires, the job is automatically canceled thus your target database gets automatically deleted.
+- A single LRS job (created by DMS) can run for a maximum of 30 days. When this period expires, the job is automatically canceled thus your target database gets automatically deleted.

articles/dms/includes/sql-virtual-machines-limitations.md

@@ -1,9 +1,9 @@
 ---
-author: MashaMSFT
+author: croblesm
+ms.author: roblescarlos
+ms.date: 01/25/2023
 ms.service: dms
 ms.topic: include
-ms.date: 01/25/2023
-ms.author: mathoma
 ---
 
 - If migrating a single database, the database backups must be placed in a flat-file structure inside a database folder (including container root folder), and the folders can't be nested, as it's not supported.