Unable to Join Replicas to Available Group – Download configuration timeout. Error 47106

Error: Availability group xxxx is not joined on the secondary replica xxxx. (Microsoft.SqlServer.Management.HadrModel) Program Location: at Microsoft.SqlServer.Management.HadrModel.HadrTask.Perform(IExecutionPolicy policy, CancellationToken token, ScenarioTaskHandler taskDelegate) at Microsoft.SqlServer.Management.Hadr.JoinDatabaseToAvailabilityGroupWorkItem.DoWork() at Microsoft.SqlServer.Management.TaskForms.SimpleWorkItem.Run() Failed to join local availability replica to availability group <ag1>. The operation encountered SQL Server error 47106 and has been rolled back. Check the SQL Server error log for... » read more

0
Read
echiang
Availability Group Cluster Type

Cluster type The possible cluster types depend on the SQL Server version and operating system. Choose one from the following list: Windows Server Failover Clustering Use when the availability group is hosted on instances of SQL Server that belong to a Windows Server failover cluster for high availability and disaster recovery. Applies to all supported... » read more

0
Read
echiang
Check Open Transaction

Using DBCC OPENTRAN Here, I show how DBCC OPENTRAN can also be used to quickly narrow down the specific problem below. When working with SSMS, have you run into a situation where you try to expand the list of tables and SQL Server came back with this nice message? Lock request time out period exceeded.... » read more

0
Read
echiang
Lock request time out period exceeded.

Error: Msg 1222, Level 16, State 24, Procedure xxxx, Line 79 [Batch Start Line 778] Lock request time out period exceeded. Resolution: The query is referencing a database in AlwaysOn and the database is corrupted. Fix the AlwaysOn database. Error 2: “lock request time out period exceeded” Error When Trying to See DB Hierarchies. Resolution... » read more

0
Read
echiang
Repair Database with CHECKDB

Repair the database with allow data loss. We will need to set the database into single user mode, run the repair and then set the database back into multi user mode. Check Database Repair Database Check Repair Database Progress DBCC CHECKDB WITH PHYSICAL_ONLY One alternative to minimize contention, is to use the WITH PHYSICAL_ONLY DBCC... » read more

0
Read
echiang
A system assertion check has failed

Error: Msg 3624, Level 20, State 1, Line 4 A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup,... » read more

0
Read
echiang
Reseed Table Identity Column

The seed is good if the current identity value is equal to or greater than the current value. Note: If you are using SQL Compare to update table, don’t run the RESEED statement. May have to run the reseed statement multiple times if there are already data rows with the existing seed. Sources: https://docs.microsoft.com/en-us/sql/t-sql/database-console-commands/dbcc-checkident-transact-sql?view=sql-server-ver15

0
Read
echiang
Backup and Restore Database Time

Database backup and restore time will depend on server and memory allocated. Example 1 Server: 2.10 GHz CPU, 4.0 GB Memory File Size Time to Backup Time to Restore 0.5 GB 10 seconds 2 GB 40 seconds 35 GB 7:50 minutes for Full 283 seconds (4.7 minutes)6:37 minutes for Full 81 GB 13:54 minutes for... » read more

0
Read
echiang
Database Restore Failed: 1453 (Insufficient quota to complete the requested service.)

Error: Msg 3203, Level 16, State 1, Line 7 Read on "H:\Backups\MyBackupFile.bak" failed: 1453(Insufficient quota to complete the requested service.) Msg 3013, Level 16, State 1, Line 7 RESTORE DATABASE is terminating abnormally. Fix 1: Remove “maxtransfersize” from restore statement. Fix 2: Restrict the max server memory setting of the Sql server to allow other... » read more

0
Read
echiang