March 24, 2016 at 2:56 pm
Has anyone ever had an issue with the trustworthy setting on a database in an availability group being altered after performing a SQL Server patch?
I was patching a SQL Server 2012 clustered AG group (11.00.5613) to SP3 + CU1 (11.00.6518) and the trustworthy setting was turned off from previously being on for every database within the availability group. All non AG databases were not affected.
Has anyone else ever have this happen?
March 24, 2016 at 4:07 pm
Did you perform failover during patching?
From what I'm seeing it may be related to the failover vs. the CU/Patch.
March 25, 2016 at 7:37 am
We did patch the AAG secondary replica nodes and manually failed over until all the nodes were complete. We did not add any new secondary replicas to the AAG from database backup copy.
My understanding was that if a database was restored or attached to a SQL server, the trustworthy setting would be set to off by default.
Article:
#0303 - SQL Server - TRUSTWORTHY property is reset to OFF by database attach or restore activity
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply