• alex.sqldba (2/10/2016)


    Hi Perry,

    This is what my configuration looks like now after some tweaking based on your reply:

    GLSQCOL3010|TCP://GLSQCOL3010.blah.local:5022|SYNCHRONOUS_COMMIT|AUTOMATIC|ALL|READ_ONLY|TCP://GLSQCOL1010.blah.local:1433

    GLSQCOL1010|TCP://GLSQCOL1010.blah.local:5022|SYNCHRONOUS_COMMIT|AUTOMATIC|ALL|READ_ONLY|TCP://GLSQCOL3010.blah.local:1433

    GLSQCOL3010|TCP://GLSQCOL3010.blah.local:5022|SYNCHRONOUS_COMMIT|AUTOMATIC|ALL|READ_ONLY|TCP://GLSQCOL3010.blah.local:1433

    GLSQCOL1010|TCP://GLSQCOL1010.blah.local:5022|SYNCHRONOUS_COMMIT|AUTOMATIC|ALL|READ_ONLY|TCP://GLSQCOL3010.blah.local:1433

    My script was just an example, you may not want to specify every replica as a readonly partner in a primary role configuration, it all depends on your design for your AG

    alex.sqldba (2/10/2016)


    So,

    As a primary then any replica will accept all connections.

    Microsoft states

    For the primary role, select a new value from the Connections in primary role drop list, as follows:

    • Allow all connections

      All connections are allowed to the databases in the primary replica. This is the default setting.

    • Allow read/write connections

      When the Application Intent property is set to ReadWrite or the Application Intent connection property is not set, the connection is allowed. Connections where the Application Intent connection property is set to ReadOnly are not allowed. This can help prevent customers from connecting a read-intent work load to the primary replica by mistake. For more information about Application Intent connection property, see Using Connection String Keywords with SQL Server Native Client.

    alex.sqldba (2/10/2016)


    As a secondary they take read-only connections

    Am I missing anything? I'm still not 100% certain I know whats going on - but that's my problem. I plan to get the 3rd node involved today and then modify the routings, lets see how I fare!

    Cheers,

    Alex

    Again Microsoft states

    For the secondary role, select a new value from the Readable secondary drop list, as follows:

    • No

      No user connections are allowed to secondary databases of this replica. They are not available for read access. This is the default setting.

    • Read-intent only

      Only read-only connections are allowed to secondary databases of this replica. The secondary database(s) are all available for read access.

    • Yes

      All connections are allowed to secondary databases of this replica, but only for read access. The secondary database(s) are all available for read access.

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

    "Ya can't make an omelette without breaking just a few eggs" 😉