Merge pull request #88624 from jovanpop-msft/patch-115

Added Missing feature check in restore process

Author: PRMerger17

articles/sql-database/sql-database-managed-instance-transact-sql-information.md

@@ -539,6 +539,16 @@ A managed instance places verbose information in error logs. There are many inte
 
 ## <a name="Issues"></a> Known issues
 
+### Missing feature check in restore process
+
+**Date:** Sep 2019
+
+`RESTORE` statement and built-in point-in time restore do not perform some nessecary cheks on restored database:
+- **DBCC CHECKDB** - `RESTORE` statement don't perform `DBCC CHECKDB` on the restored database. If a original database is corrupted, automatic backups will not be taken and Azure support will contact the customer. 
+- Built-in Point-in-time restore proces don't check does the automated backup from Business Critical instance contain the [In-memory OLTP objects](sql-database-in-memory.md#in-memory-oltp). 
+
+**Workaround**: Make sure that you are executing `DBCC CHECKDB` on the source database before taking a backup, and using `WITH CHECKSUM` option in backup to avoid potential corrutions that could be restored on Managed instance. Make sure that your source database don't contain [In-memory OLTP objects](sql-database-in-memory.md#in-memory-oltp) if you are restoring it on General Purpose tier.
+
 ### Resource Governor on Business Critical service tier might need to be reconfigured after failover
 
 **Date:** Sep 2019