SSMS state will show Restoring- import changes from KB 956005

KB 956005 will be retiring

Author: PiJoCoder

docs/database-engine/database-mirroring/mirroring-states-sql-server.md

@@ -32,7 +32,7 @@ ms.author: mikeray
 |Mirroring state|Description|  
 |---------------------|-----------------|  
 |SYNCHRONIZING|The contents of the mirror database are lagging behind the contents of the principal database. The principal server is sending log records to the mirror server, which is applying the changes to the mirror database to roll it forward.<br /><br /> At the start of a database mirroring session, the database is in the SYNCHRONIZING state. The principal server is serving the database, and the mirror is trying to catch up.|  
-|SYNCHRONIZED|When the mirror server becomes sufficiently caught up to the principal server, the mirroring state changes to SYNCHRONIZED. The database remains in this state as long as the principal server continues to send changes to the mirror server and the mirror server continues to apply changes to the mirror database.<br /><br /> If transaction safety is set to FULLautomatic failover and manual failover are both supported in the SYNCHRONIZED state, there is no data loss after a failover.<br /><br /> If transaction safety is off, some data loss is always possible, even in the SYNCHRONIZED state.|  
+|SYNCHRONIZED|When the mirror server becomes sufficiently caught up to the principal server, the mirroring state changes to SYNCHRONIZED. The database remains in this state as long as the principal server continues to send changes to the mirror server and the mirror server continues to apply changes to the mirror database.<br /><br /> If transaction safety is set to FULLautomatic failover and manual failover are both supported in the SYNCHRONIZED state, there is no data loss after a failover.<br /><br /> If transaction safety is off, some data loss is always possible, even in the SYNCHRONIZED state.<br /><br /> **Note:** In SQL Server Management Studio the status of the database will show as Restoring. For actual status you can query mirroring_state_desc column in the [sys.database_mirroring](https://docs.microsoft.com/sql/relational-databases/system-catalog-views/sys-database-mirroring-transact-sql) |  
 |SUSPENDED|The mirror copy of the database is not available. The principal database is running without sending any logs to the mirror server, a condition known as *running exposed*. This is the state after a failover.<br /><br /> A session can also become SUSPENDED as a result of redo errors or if the administrator pauses the session.<br /><br /> SUSPENDED is a persistent state that survives partner shutdowns and startups.|  
 |PENDING_FAILOVER|This state is found only on the principal server after a failover has begun, but the server has not transitioned into the mirror role.<br /><br /> When the failover is initiated, the principal database goes into the PENDING_FAILOVER state, quickly terminates any user connections, and takes over the mirror role soon thereafter.|  
 |DISCONNECTED|The partner has lost communication with the other partner.|