Post reply

Verify Read Only Routing using Profiler

  • February 26, 2019 at 12:56 am

    #379459

    How can I verify the readonly routing is working fine with Profiler?

    I connected to listener using Application Intent=Read Only and ran a select query but the hit is going to primary server only when checked by running profiler on both primary & secondary.

  • February 26, 2019 at 9:15 am

    #2022987

    First, don't use profiler anymore. Use Extended Events or the xEvent Profiler to watch things.

    Second, do you have the primary set for read/write? This should limit the read only connections.

  • February 26, 2019 at 10:23 pm

    #2023045

    Steve Jones - SSC Editor - Tuesday, February 26, 2019 9:15 AM

    First, don't use profiler anymore. Use Extended Events or the xEvent Profiler to watch things.

    Second, do you have the primary set for read/write? This should limit the read only connections.

    Thanks Steve. Primary is set to allow all connections, will change that to Read\Write and will use EE or xEvent Profiler.

    Thanks Again

  • February 27, 2019 at 8:48 am

    #2023084

    Good luck. I haven't had issues here, but I do see the docs mentioning that setting to read/write should make clients prefer the secondary.

  • February 27, 2019 at 10:43 pm

    #2023160

    Steve Jones - SSC Editor - Wednesday, February 27, 2019 8:48 AM

    Good luck. I haven't had issues here, but I do see the docs mentioning that setting to read/write should make clients prefer the secondary.

    Thanks a lot Steve. Changing the setting to Read\Write worked.

  • February 28, 2019 at 9:05 am

    #2023214

    Excellent. Glad to hear it and hope everything else is working great.

Viewing 6 posts - 1 through 5 (of 5 total)

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