Merge pull request #13566 from MashaMSFT/20200122_fixes

TedA-M · web-flow · commit ed6698f561ae · 2020-02-10T15:46:50.000-08:00
Misc fixes based on issues
diff --git a/docs/database-engine/availability-groups/windows/configure-backup-on-availability-replicas-sql-server.md b/docs/database-engine/availability-groups/windows/configure-backup-on-availability-replicas-sql-server.md
@@ -156,11 +156,11 @@ ms.author: mathoma
 ##  <a name="FollowUp"></a> Follow Up: After Configuring Backup on Secondary Replicas  
  To take the automated backup preference into account for a given availability group, on each server instance that hosts an availability replica whose backup priority is greater than zero (>0), you need to script backup jobs for the databases in the availability group. To determine whether the current replica is the preferred backup replica, use the [sys.fn_hadr_backup_is_preferred_replica](../../../relational-databases/system-functions/sys-fn-hadr-backup-is-preferred-replica-transact-sql.md) function in your backup script. If the availability replica that is hosted by the current server instance is the preferred replica for backups, this function returns 1. If not, the function returns 0. By running a simple script on each availability replica that queries this function, you can determine which replica should run a given backup job. For example, a typical snippet of a backup-job script would look like:  
   
-```  
+```sql  
 IF (NOT sys.fn_hadr_backup_is_preferred_replica(@DBNAME))  
 BEGIN  
       Select 'This is not the preferred replica, exiting with success';  
-      RETURN 0 - This is a normal, expected condition, so the script returns success  
+      RETURN 0 -- This is a normal, expected condition, so the script returns success  
 END  
 BACKUP DATABASE @DBNAME TO DISK=<disk>  
    WITH COPY_ONLY;  
diff --git a/docs/database-engine/availability-groups/windows/configure-distributed-availability-groups.md b/docs/database-engine/availability-groups/windows/configure-distributed-availability-groups.md
@@ -2,7 +2,7 @@
 title: "Configure a distributed availability group"
 description: "Describes how to create and configure an Always On distributed availability group. " 
 ms.custom: "seodec18"
-ms.date: "08/17/2017"
+ms.date: "01/28/2020"
 ms.prod: sql
 ms.reviewer: ""
 ms.technology: high-availability
@@ -140,7 +140,7 @@ GO
 ### Create a listener for  the secondary availability group  
  Next add a listener for the secondary availability group on the second WSFC. In this example, the listener is named `ag2-listener`. For detailed instructions on creating a listener, see [Create or Configure an Availability Group Listener &#40;SQL Server&#41;](../../../database-engine/availability-groups/windows/create-or-configure-an-availability-group-listener-sql-server.md).  
   
-```  
+```sql  
 ALTER AVAILABILITY GROUP [ag2]    
     ADD LISTENER 'ag2-listener' ( WITH IP ( ('2001:db88:f0:f00f::cf3c'),('2001:4898:e0:f213::4ce2') ) , PORT = 60173);    
 GO  
@@ -222,15 +222,15 @@ ALTER DATABASE [db1] SET HADR AVAILABILITY GROUP = [ag2];
 
 Only manual failover is supported at this time. To manually fail over a distributed availability group:
 
-1. To ensure that no data is lost, set the distributed availability group to synchronous commit.
-1. Wait until the distributed availability group is synchronized.
+1. To ensure that no data is lost, stop all transactions on the global primary databases (that is, databases of the primary availability group), then set the distributed availability group to synchronous commit.
+1. Wait until the distributed availability group is synchronized and has the same last_hardened_lsn per database. 
 1. On the global primary replica, set the distributed availability group role to `SECONDARY`.
 1. Test failover readiness.
 1. Fail over the primary availability group.
 
 The following Transact-SQL examples demonstrate the detailed steps to fail over the distributed availability group named `distributedag`:
 
-1. Set the distributed availability group to synchronous commit by running the following code on *both* the global primary and the forwarder.   
+1. To ensure that no data is lost, stop all transactions on the global primary databases (that is, databases of the primary availability group). Then set the distributed availability group to synchronous commit by running the following code on *both* the global primary and the forwarder.   
     
       ```sql  
       -- sets the distributed availability group to synchronous commit 
@@ -256,24 +256,29 @@ The following Transact-SQL examples demonstrate the detailed steps to fail over
        GO
 
       ```  
-   >[!NOTE]
-   >In a distributed availability group, the synchronization status between the two availability groups depends on the availability mode of both replicas. For synchronous commit mode, both the current primary availability group, and the current secondary availability group must have `SYNCHRONOUS_COMMIT` availability mode. For this reason, you must run the script above on both the global primary replica, and the forwarder.
+   > [!NOTE]
+   > In a distributed availability group, the synchronization status between the two availability groups depends on the availability mode of both replicas. For synchronous commit mode, both the current primary availability group, and the current secondary availability group must have `SYNCHRONOUS_COMMIT` availability mode. For this reason, you must run the script above on both the global primary replica, and the forwarder.
+
 
-1. Wait until the status of the distributed availability group has changed to `SYNCHRONIZED`. Run the following query on the global primary, which is the primary replica of the primary availability group. 
+1. Wait until the status of the distributed availability group has changed to `SYNCHRONIZED` and all replicas have the same last_hardened_lsn (per database). Run the following query on both the global primary, which is the primary replica of the primary availability group, and the forwarder to check the synchronization_state_desc and last_hardened_lsn: 
     
       ```sql  
+      -- Run this query on the Global Primary and the forwarder
+      -- Check the results to see if synchronization_state_desc is SYNCHRONIZED, and the last_hardened_lsn is the same per database on both the global primary and       forwarder 
+      -- If not rerun the query on both side every 5 seconds until it is the case
+      --
       SELECT ag.name
              , drs.database_id
+             , db_name(drs.database_id) as database_name
              , drs.group_id
              , drs.replica_id
              , drs.synchronization_state_desc
-             , drs.end_of_log_lsn 
-        FROM sys.dm_hadr_database_replica_states drs,
-        sys.availability_groups ag
-          WHERE drs.group_id = ag.group_id;      
+             , drs.last_hardened_lsn  
+      FROM sys.dm_hadr_database_replica_states drs 
+      INNER JOIN sys.availability_groups ag on drs.group_id = ag.group_id;
       ```  
 
-    Proceed after the availability group **synchronization_state_desc** is `SYNCHRONIZED`. If **synchronization_state_desc** is not `SYNCHRONIZED`, run the command every five seconds until it changes. Do not proceed until the **synchronization_state_desc** = `SYNCHRONIZED`. 
+    Proceed after the availability group **synchronization_state_desc** is `SYNCHRONIZED`, and the last_hardened_lsn is the same per database on both the global primary and forwarder.  If **synchronization_state_desc** is not `SYNCHRONIZED` or last_hardened_lsn is not the same, run the command every five seconds until it changes. Do not proceed until the **synchronization_state_desc** = `SYNCHRONIZED` and last_hardened_lsn is the same per database. 
 
 1. On the global primary, set the distributed availability group role to `SECONDARY`. 
 
@@ -283,23 +288,41 @@ The following Transact-SQL examples demonstrate the detailed steps to fail over
 
     At this point, the distributed availability group is not available.
 
-1. Test the failover readiness. Run the following query:
+1. Test the failover readiness. Run the following query on both the global primary and the forwarder:
 
     ```sql
-    SELECT ag.name, 
-        drs.database_id, 
-        drs.group_id, 
-        drs.replica_id, 
-        drs.synchronization_state_desc, 
-        drs.end_of_log_lsn 
-    FROM sys.dm_hadr_database_replica_states drs, sys.availability_groups ag
-    WHERE drs.group_id = ag.group_id; 
+     -- Run this query on the Global Primary and the forwarder
+     -- Check the results to see if the last_hardened_lsn is the same per database on both the global primary and forwarder 
+     -- The availability group is ready to fail over when the last_hardened_lsn is the same for both availability groups per database
+     --
+     SELECT ag.name, 
+         drs.database_id, 
+         db_name(drs.database_id) as database_name,
+         drs.group_id, 
+         drs.replica_id,
+         drs.last_hardened_lsn
+     FROM sys.dm_hadr_database_replica_states drs
+     INNER JOIN sys.availability_groups ag ON drs.group_id = ag.group_id;
     ```  
-    The availability group is ready to fail over when the **synchronization_state_desc** is `SYNCHRONIZED` and the **end_of_log_lsn** is the same for both availability groups. 
 
-1. Fail over from the primary availability group to the secondary availability group. Run the following command on the SQL Server that hosts the primary replica for the secondary availability group. 
+    The availability group is ready to fail over when the **last_hardened_lsn** is the same for both availability groups per database. If the last_hardened_lsn is not the same after a period of time, to avoid data loss, fail back to the global primary by running this command on the global primary and then start over from the second step: 
+
+    ```sql
+    -- If the last_hardened_lsn is not the same after a period of time, to avoid data loss, 
+    -- we need to fail back to the global primary by running this command on the global primary 
+    -- and then start over from the second step:
+
+    ALTER AVAILABILITY GROUP distributedag FORCE_FAILOVER_ALLOW_DATA_LOSS; 
+    ```
+
+
+1. Fail over from the primary availability group to the secondary availability group. Run the following command on the forwarder, the SQL Server that hosts the primary replica of the secondary availability group. 
 
     ```sql
+    -- Once the last_hardened_lsn is the same per database on both sides
+    -- We can Fail over from the primary availability group to the secondary availability group. 
+    -- Run the following command on the forwarder, the SQL Server instance that hosts the primary replica of the secondary availability group.
+
     ALTER AVAILABILITY GROUP distributedag FORCE_FAILOVER_ALLOW_DATA_LOSS; 
     ```  
 
diff --git a/docs/relational-databases/errors-events/database-engine-events-and-errors.md b/docs/relational-databases/errors-events/database-engine-events-and-errors.md
@@ -1,7 +1,7 @@
 ---
 title: "Database engine events and errors"
 ms.custom: ""
-ms.date: 01/11/2019
+ms.date: 01/28/2020
 ms.prod: sql
 ms.reviewer: ""
 ms.technology: supportability
@@ -14,6 +14,17 @@ ms.author: mathoma
 
 The table contains error message numbers and the description, which is the text of the error message from the sys.messages catalog view. Where applicable, the error number is a link to further information.
 
+This list is not exhaustive. For a full list of all errors, query the sys.messages catalog view with the following query:
+
+```sql
+SELECT message_id AS Error, severity AS Severity,  
+[Event Logged] = CASE is_event_logged WHEN 0 THEN 'No' ELSE 'Yes' END,
+text AS [Description]
+FROM sys.messages
+WHERE language_id = <desired language, such as 1033 for US English>
+ORDER BY message_id
+```
+
 ## Errors -2 to 999
 
 | Error| Severity | Event Logged | Description|
@@ -568,8 +579,32 @@ The table contains error message numbers and the description, which is the text
 |	971	|	10	|	No	|	The resource database has been detected in two different locations. Attaching the resource database in the same directory as sqlservr.exe at '%.*ls' instead of the currently attached resource database at '%.*ls'.	|
 |	972	|	17	|	No	|	Could not use database '%d' during procedure execution.	|
 |	973	|	10	|	Yes	|	Database %ls was started . However, FILESTREAM is not compatible with the READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION options. Either remove the FILESTREAM files and the FILESTREAM filegroups, or set READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION to OFF.	|
+|974 | 10  | No  |  Attaching the resource database in the same directory as sqlservr.exe at '%.*ls' failed as the database files do not exist.|
+|975 | 10  | Yes |  System objects could not be updated in database '%.*ls' because it is read-only. |
+|976 | 14  | No  |  The target database, '%.*ls', is participating in an availability group and is currently not accessible for queries. Either data movement is suspended or the availability replica is not enabled for read access. To allow read-only access to this and other d |
+|977 | 10 |  No  |  Warning: Could not find associated index for the constraint '%.*ls' on object_id '%d' in database '%.*ls'.|
+|978 | 14 |  No  |  The target database ('%.*ls') is in an availability group and is currently accessible for connections when the application intent is set to read only. For more information about application intent, see SQL Server Books Online. |
+|979  | 14 | No  |  The target database ('%.*ls') is in an availability group and currently does not allow read only connections. For more information about application intent, see SQL Server Books Online.|
+|980 |  21 |  Yes |  SQL Server cannot load database '%.*ls' because it contains a columnstore index. The currently installed edition of SQL Server |does not support columnstore indexes. Either disable the columnstore index in the database by using a supported edition of SQL Se|
+|981  |  10 | No | Database manager will be using %d target database version. |
+|982  |  14 | No | Unable to access the '%.*ls' database because no online secondary replicas are enabled for read-only access. Check the availability group configuration to verify that at least one secondary replica is configured for read-only access. Wait for an enabled re|
+|983 |  14  | No | Unable to access availability database '%.*ls' because the database replica is not in the PRIMARY or SECONDARY role. Connections to an availability database is permitted only when the database replica is in the PRIMARY or SECONDARY role. Try the operation |
+|984 | 21  | Yes | Failed to perform a versioned copy of sqlscriptdowngrade.dll from Binn to Binn\Cache folder. VerInstallFile API failed with error code %d.|
+|985 |  10 | Yes  |      Successfully installed the file '%ls' into folder '%ls'. |
+|986 |  10 | No   |     Couldn't get a clean bootpage for database  '%.*ls' after %d tries. This is an informational message only. No user action is required. |
+|987 |  23  |    Yes | A duplicate key insert was hit when updating system objects in database '%.*ls'.|
+|988 |  14  |    No  | Unable to access database '%.*ls' because it lacks a quorum of nodes for high availability. Try the operation again later.|
+|989 |  16  |    No  | Failed to take the host database with ID %d offline when one or more of its partition databases is marked as suspect.|
+|990 |  16  |    No  | Taking the host database with ID %d offline because one or more of its partition databases is marked as suspect.|
+|991 |  16  |    No  | Failed to take the host database '%.*ls' offline when one or more of its partition databases is marked as suspect.|
+|992 |  16  |    No  | Failed to get the shared lock on database '%.*ls'.|
+|993 |  10  |    No  | Redo for database '%.*ls' applied version upgrade step from %d to %d.|
+|994 |  10  |    No  | Warning: Index "%.*ls" on "%.*ls"."%.*ls" is disabled because it contains a computed column.|
+|995 |  10  |    No  | Warning: Index "%.*ls" on "%.*ls"."%.*ls" is disabled. It cannot be upgraded as it resides on a read-only filegroup.|
+|996 |  10  |    No  | Warning: Index "%.*ls" on "%.*ls"."%.*ls" is disabled. This columnstore index cannot be upgraded, likely because it exceeds the row size limit of '%d' bytes.|
 |	&nbsp;	|	&nbsp;	|&nbsp;		|	&nbsp;	|
 
+
 ## Errors 1000 to 1999
 
 | Error| Severity | Event Logged | Description|
@@ -2152,11 +2187,12 @@ The table contains error message numbers and the description, which is the text
 |	4863	|	16	|	No	|	Bulk load data conversion error (truncation) for row %d, column %d (%ls).	|
 |	4864	|	16	|	No	|	Bulk load data conversion error (type mismatch or invalid character for the specified codepage) for row %d, column %d (%ls).	|
 |	4865	|	16	|	No	|	Cannot bulk load because the maximum number of errors (%d) was exceeded.	|
-|	4866	|	16	|	No	|	The bulk load failed. The column is too long in the data file for row %d, column %d. Verify that the field terminator and row terminator are specified correctly.	|
+|	4866	|	16	|	No	|	The bulk load failed. The column is too long in the data file for row %d, column %d. Verify that the field terminator and row terminator are specified correctly.	| Bulk load failed due to invalid column value in CSV data file %ls in row %d, column %d | 
 |	4867	|	16	|	No	|	Bulk load data conversion error (overflow) for row %d, column %d (%ls).	|
 |	4868	|	16	|	No	|	The bulk load failed. The codepage "%d" is not installed. Install the codepage and run the command again.	|
 |	4869	|	16	|	No	|	The bulk load failed. Unexpected NULL value in data file row %d, column %d. The destination column (%ls) is defined as NOT NULL.	|
 |	4870	|	16	|	No	|	Cannot bulk load because of an error writing file "%ls". Operating system error code %ls.	|
+|   4879    |   16  |   No  | 
 |	4871	|	16	|	No	|	Bulk load error while attempting to log errors.	|
 |	4872	|	16	|	No	|	Line %d in format file "%ls": duplicate element id "%ls".	|
 |	4873	|	16	|	No	|	Line %d in format file "%ls": referencing non-existing element id "%ls".	|
diff --git a/docs/relational-databases/errors-events/mssqlserver-18456-database-engine-error.md b/docs/relational-databases/errors-events/mssqlserver-18456-database-engine-error.md
@@ -67,6 +67,7 @@ To increase security, the error message that is returned to the client deliberat
 |12|Login is valid login, but server access failed.|  
 |18|Password must be changed.|  
 |38, 46|Could not find database requested by user.|
+|58| When SQL Server is set to use Windows Authentication only, and a client attempts to log in using SQL authentication. Another cause is when SIDs do not match.|
 |102 - 111|AAD failure.|
 |122 - 124|Failure due to empty user name or password.|
 |126|Database requested by user does not exist.|
