Always On Availability Group -- Disk resize on the secondary replica
Hi, We currently have a 2 node on Always ON Availability group with a cloud witness. Recently, we found the need to resize the data file disk. This 2 nodes are SQL Server on Azure VM. Find below our current situation 1st Resize on the secondary node (read-only) Resizing first on the secondary node - we noticed that the disk type changed from Basic to Dynamic mode and having seen some documentation on internet -- https://lokna.no/?p=1384 we thought of been cautious of having the disk in dynamic mode. As a result of the above, we did not proceed to resizing the the production until we are sure. Question Is it save to proceed with disk in dynamic mode? What if we proceed and the primary is still on Basic mode, is it OK to have the disk type of primary node as Basic and the disk type of secondary as Dynamic? Thanks
Why does changing the sql server service account provide connection for replicas
I have a question to better understand availability groups(AG). I have tested it several times and it is always the same. When I create an AG, the connection of the replicas does not work. My solution was as follows. In sql server configuration manager I changed the account for the service of the sql server. I did this for both instances. As a new account I created a local user and gave him a Sql Server login. Microsoft does not specify anything about this? Why do I have to do this?