How to fix Database might contain bulk logged changes that have not been backed up for Always On

Question: I'm trying to add a new database to an existing Clustered Always On High Availability Group , but every time I execute the following statement , I get the error message below alter availability group MY_AG1 add database [mydb]; Msg 1475, Level 16, State 105, Line 5 Database "mydb" might contain bulk logged changes that have not been backed up. Take a log backup on the principal database or primary database. Then restore this backup either on the mirror database to enable database mirroring or on every secondary database to enable you to join it to the availability group.... Read more →

Quick access to SQL Server Always On Availability cheatsheet

These are queries to manage SQL Server AlwaysOn Availability Groups Using sys.fn_hadr_is_primary_replica to identify if the database is primary replica SELECT sys.fn_hadr_is_primary_replica ('my_ag_db'); Display All availability groups visible to this server when the Server is the Primary replica SELECT Groups.[Name] AS AGname FROM sys.dm_hadr_availability_group_states States INNER JOIN master.sys.availability_groups Groups ON States.group_id = Groups.group_id WHERE primary_replica = @@Servername; Display All availability groups visible to this server when this Server is a Secondary replica SELECT Groups.[Name] AS AGname FROM sys.dm_hadr_availability_group_states States INNER JOIN master.sys.availability_groups Groups ON States.group_id = Groups.group_id WHERE primary_replica != @@Servername; Display All Databases Across all Availability groups within the... Read more →