Post reply

Contained Availability Groups in SQL Server 2022

  • August 20, 2025 at 12:00 am

    #4635069

    Comments posted to this topic are about the item Contained Availability Groups in SQL Server 2022

  • August 21, 2025 at 12:10 am

    #4638400

    Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • September 1, 2025 at 8:52 am

    #4643967

    You posted "After you create the Availability Group, SQL Server automatically adds two additional system databases—SQLAG-2022_master and SQLAG-2022_msdb". However, in the picture the new system databases are not in the system databases folder. Are they indeed system databases ?

    I notice also that when creating a login (user1 as you posted) that you dont see this login unless you create it by connecting to the AG listener. Then you connected to the replica and mentioned you will not see it there because the connection is to the instance. I dont know if you mentioned this, but will you see it if you connect to the replicas AG listener ?

    Thank you

    ----------------------------------------------------

  • September 2, 2025 at 6:28 am

    #4644430

    You posted "After you create the Availability Group, SQL Server automatically adds two additional system databases—SQLAG-2022_master and SQLAG-2022_msdb". However, in the picture the new system databases are not in the system databases folder. Are they indeed system databases ? - Yes, these databases contains system objects such as logins, jobs in the context of Availability Group. Means whatever objects are created by connecting to listener, those will appear in the system tables of these databases and not in the instance's system tables(system databases).

    I notice also that when creating a login (user1 as you posted) that you dont see this login unless you create it by connecting to the AG listener. Then you connected to the replica and mentioned you will not see it there because the connection is to the instance. I dont know if you mentioned this, but will you see it if you connect to the replicas AG listener ? - If you create a login by connecting with AG Listener and then if you connect with replica name, you won't be able to see those logins. The reason being those logins are available in the context of AG and available to see with listener only. Even if you check with replica(SQL Instance) name, you won't be able to see them. You need to make sure that logins are specifically created by connecting with replica name so that you can see them inside replica's.

    Hope I am able to answer your queries.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply