This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
I'm setting up an Always On following the whole procedure I found in other laboratories and I notice that mine happens differently.
The database goes online only after I run it (Join to Availability Group ...)
What can be wrong?
I attached all the settings I made.
Thank you.
What service account of SQL Server on all three instances you have used ? Are they same do they have connect permission on end points ?
Can you run sp_readerrorlog on one of the secondary databases and post output here
I am attaching the results.
Tks.
I do not see any issue related to Replicas not being added, may be it is taking time. I believe Yuximiao is correct in her observation
Hi @Salves ,
Do you refresh your AG01? Try to refresh it firstly if it does not work.
As your screenshot, just click Join to Avalibility Group and then click ok and then refresh, that will be done.
BR,
Mia
@Yuximiao-MSFT ,
if i do it works perfectly! But is this normal when we create AG the first time?
I see in the tutorials that always go online doing nothing!
Thank you.
@Salves ,
I reproduced your issue yesterday, firstly it is not online, then I refresh and join to avalibility gorup and then ok.
It tells me already join to avalibility group and then I refresh, it turns ok.
It needs time to recovery I think.
Quote from this :select-initial-data-synchronization-page-always-on-availability-group-wizards
...Then, on every server instance that hosts one of the new secondary replicas, the wizard will create the secondary databases by restoring backups using RESTORE WITH NORECOVERY. After creating each of the secondary databases, the wizard will join the new secondary database to the availability group. As soon as a secondary database is joined, data synchronizations starts on that database....
If the reply is helped, please do "Accept Answer".
BR,
Mia
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 1%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EN%3C/text%3E%3C/svg%3E)
What is SSMS version you use? If you use old SSMS version, there might be the issue you are facing due to a bug.
So you should try to use latest SSMS version.