SQL Server Primary Login RestrictionsApplicationIntent=ReadOnly Traffic when no Readable Secondary AvailableAvailability Group: ReadIntent connection failingAlways On Availability Group, Always redirect user to read only instanceAlwaysON - Force users connection to use Readable Secondary NodesConnection to secondary DB in AlwaysOn High AvailabilityLoad balancing reads SQL Server 2016 AGAlways On Availability Group ApplicationIntent=ReadOnly Not routing to SecondaryQuestions on Availability Group Readable Secondaryhow do I ensure that users in AlwaysOn Availability Group only connect to the secondary, even in a failoverHow to let particular logins to work on the secondary replica only?

Schematic conventions for different supply rails

Sword in the Stone story where the sword was held in place by electromagnets

What are the possible solutions of the given equation?

Why is a Java array index expression evaluated before checking if the array reference expression is null?

Does the statement `int val = (++i > ++j) ? ++i : ++j;` invoke undefined behavior?

Official degrees of earth’s rotation per day

How to deal with taxi scam when on vacation?

Citation at the bottom for subfigures in beamer frame

Bastion server: use TCP forwarding VS placing private key on server

How do I hide Chekhov's Gun?

How to answer questions about my characters?

How to generate globally unique ids for different tables of the same database?

Where is the 1/8 CR apprentice in Volo's Guide to Monsters?

Instead of Universal Basic Income, why not Universal Basic NEEDS?

Why doesn't the EU now just force the UK to choose between referendum and no-deal?

Can hydraulic brake levers get hot when brakes overheat?

Bash: What does "masking return values" mean?

Employee lack of ownership

Have researchers managed to "reverse time"? If so, what does that mean for physics?

Why does Deadpool say "You're welcome, Canada," after shooting Ryan Reynolds in the end credits?

Russian cases: A few examples, I'm really confused

Can elves maintain concentration in a trance?

SQL Server Primary Login Restrictions

Make a transparent 448*448 image



SQL Server Primary Login Restrictions


ApplicationIntent=ReadOnly Traffic when no Readable Secondary AvailableAvailability Group: ReadIntent connection failingAlways On Availability Group, Always redirect user to read only instanceAlwaysON - Force users connection to use Readable Secondary NodesConnection to secondary DB in AlwaysOn High AvailabilityLoad balancing reads SQL Server 2016 AGAlways On Availability Group ApplicationIntent=ReadOnly Not routing to SecondaryQuestions on Availability Group Readable Secondaryhow do I ensure that users in AlwaysOn Availability Group only connect to the secondary, even in a failoverHow to let particular logins to work on the secondary replica only?













4















I have read only routing setup and working fine. I have a SQL login that accesses the readable secondary via the listener using ApplicationIntent=ReadOnly. However I want to prevent the user from accessing the primary.



I have seen a lot of topics on this and they all seem to suggest disabling the login on the primary. When I do this connections to the listener with ApplicationIntent=ReadOnly fail with Login failed for user ''. Reason: The account is disabled.



I have ensured the accounts are the same SID.



Thanks for any help.










share|improve this question
























  • No, I checked that. I can connect to the secondary directly with the account

    – Dustin Laine
    4 hours ago












  • Can you please be more specific on this point, "However I want to prevent the user from accessing the primary." as it will change my answer.

    – Sean Gallardy
    4 hours ago











  • The user should not be able to connect to the primary replica, only secondary.

    – Dustin Laine
    4 hours ago















4















I have read only routing setup and working fine. I have a SQL login that accesses the readable secondary via the listener using ApplicationIntent=ReadOnly. However I want to prevent the user from accessing the primary.



I have seen a lot of topics on this and they all seem to suggest disabling the login on the primary. When I do this connections to the listener with ApplicationIntent=ReadOnly fail with Login failed for user ''. Reason: The account is disabled.



I have ensured the accounts are the same SID.



Thanks for any help.










share|improve this question
























  • No, I checked that. I can connect to the secondary directly with the account

    – Dustin Laine
    4 hours ago












  • Can you please be more specific on this point, "However I want to prevent the user from accessing the primary." as it will change my answer.

    – Sean Gallardy
    4 hours ago











  • The user should not be able to connect to the primary replica, only secondary.

    – Dustin Laine
    4 hours ago













4












4








4








I have read only routing setup and working fine. I have a SQL login that accesses the readable secondary via the listener using ApplicationIntent=ReadOnly. However I want to prevent the user from accessing the primary.



I have seen a lot of topics on this and they all seem to suggest disabling the login on the primary. When I do this connections to the listener with ApplicationIntent=ReadOnly fail with Login failed for user ''. Reason: The account is disabled.



I have ensured the accounts are the same SID.



Thanks for any help.










share|improve this question
















I have read only routing setup and working fine. I have a SQL login that accesses the readable secondary via the listener using ApplicationIntent=ReadOnly. However I want to prevent the user from accessing the primary.



I have seen a lot of topics on this and they all seem to suggest disabling the login on the primary. When I do this connections to the listener with ApplicationIntent=ReadOnly fail with Login failed for user ''. Reason: The account is disabled.



I have ensured the accounts are the same SID.



Thanks for any help.







sql-server availability-groups sql-server-2017






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 4 hours ago







Dustin Laine

















asked 4 hours ago









Dustin LaineDustin Laine

1766




1766












  • No, I checked that. I can connect to the secondary directly with the account

    – Dustin Laine
    4 hours ago












  • Can you please be more specific on this point, "However I want to prevent the user from accessing the primary." as it will change my answer.

    – Sean Gallardy
    4 hours ago











  • The user should not be able to connect to the primary replica, only secondary.

    – Dustin Laine
    4 hours ago

















  • No, I checked that. I can connect to the secondary directly with the account

    – Dustin Laine
    4 hours ago












  • Can you please be more specific on this point, "However I want to prevent the user from accessing the primary." as it will change my answer.

    – Sean Gallardy
    4 hours ago











  • The user should not be able to connect to the primary replica, only secondary.

    – Dustin Laine
    4 hours ago
















No, I checked that. I can connect to the secondary directly with the account

– Dustin Laine
4 hours ago






No, I checked that. I can connect to the secondary directly with the account

– Dustin Laine
4 hours ago














Can you please be more specific on this point, "However I want to prevent the user from accessing the primary." as it will change my answer.

– Sean Gallardy
4 hours ago





Can you please be more specific on this point, "However I want to prevent the user from accessing the primary." as it will change my answer.

– Sean Gallardy
4 hours ago













The user should not be able to connect to the primary replica, only secondary.

– Dustin Laine
4 hours ago





The user should not be able to connect to the primary replica, only secondary.

– Dustin Laine
4 hours ago










1 Answer
1






active

oldest

votes


















5















I have a SQL login that accesses the readable secondary via the listener using ApplicationIntent=ReadOnly. However I want to prevent the user from accessing the primary.




More specifically:




The user should not be able to connect to the primary replica, only secondary.




In this case, it's not possible to do what you're wanting. You can't use read only routing with this as the first step in read only routing is to connect to the primary to check if the requirements to meet read only routing are correctly used and then get the metadata from the primary to understand where the new connection should take place.



You can, however, use something such as a network load balance appliance to dynamically update a cname or A record (AAAA if IPv6) to always point to a secondary. This would be specific to the load balancing software/hardware you choose to use. You could also write your own with a trivial amount of work.






share|improve this answer























  • I think you cleared this up, but please let me confirm. Reading the information I previously found there is obscurity in if a listener is used. In my scenario I can still connect to the secondary directly using the disabled login approach, but they would not benefit from the routing features of the AG. If I want to use the listener then the login needs to exist and be enabled on both. Does this sound right?

    – Dustin Laine
    3 hours ago











  • @DustinLaine Correct (disabled login on the primary)!

    – Sean Gallardy
    2 hours ago










Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "182"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f232174%2fsql-server-primary-login-restrictions%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









5















I have a SQL login that accesses the readable secondary via the listener using ApplicationIntent=ReadOnly. However I want to prevent the user from accessing the primary.




More specifically:




The user should not be able to connect to the primary replica, only secondary.




In this case, it's not possible to do what you're wanting. You can't use read only routing with this as the first step in read only routing is to connect to the primary to check if the requirements to meet read only routing are correctly used and then get the metadata from the primary to understand where the new connection should take place.



You can, however, use something such as a network load balance appliance to dynamically update a cname or A record (AAAA if IPv6) to always point to a secondary. This would be specific to the load balancing software/hardware you choose to use. You could also write your own with a trivial amount of work.






share|improve this answer























  • I think you cleared this up, but please let me confirm. Reading the information I previously found there is obscurity in if a listener is used. In my scenario I can still connect to the secondary directly using the disabled login approach, but they would not benefit from the routing features of the AG. If I want to use the listener then the login needs to exist and be enabled on both. Does this sound right?

    – Dustin Laine
    3 hours ago











  • @DustinLaine Correct (disabled login on the primary)!

    – Sean Gallardy
    2 hours ago















5















I have a SQL login that accesses the readable secondary via the listener using ApplicationIntent=ReadOnly. However I want to prevent the user from accessing the primary.




More specifically:




The user should not be able to connect to the primary replica, only secondary.




In this case, it's not possible to do what you're wanting. You can't use read only routing with this as the first step in read only routing is to connect to the primary to check if the requirements to meet read only routing are correctly used and then get the metadata from the primary to understand where the new connection should take place.



You can, however, use something such as a network load balance appliance to dynamically update a cname or A record (AAAA if IPv6) to always point to a secondary. This would be specific to the load balancing software/hardware you choose to use. You could also write your own with a trivial amount of work.






share|improve this answer























  • I think you cleared this up, but please let me confirm. Reading the information I previously found there is obscurity in if a listener is used. In my scenario I can still connect to the secondary directly using the disabled login approach, but they would not benefit from the routing features of the AG. If I want to use the listener then the login needs to exist and be enabled on both. Does this sound right?

    – Dustin Laine
    3 hours ago











  • @DustinLaine Correct (disabled login on the primary)!

    – Sean Gallardy
    2 hours ago













5












5








5








I have a SQL login that accesses the readable secondary via the listener using ApplicationIntent=ReadOnly. However I want to prevent the user from accessing the primary.




More specifically:




The user should not be able to connect to the primary replica, only secondary.




In this case, it's not possible to do what you're wanting. You can't use read only routing with this as the first step in read only routing is to connect to the primary to check if the requirements to meet read only routing are correctly used and then get the metadata from the primary to understand where the new connection should take place.



You can, however, use something such as a network load balance appliance to dynamically update a cname or A record (AAAA if IPv6) to always point to a secondary. This would be specific to the load balancing software/hardware you choose to use. You could also write your own with a trivial amount of work.






share|improve this answer














I have a SQL login that accesses the readable secondary via the listener using ApplicationIntent=ReadOnly. However I want to prevent the user from accessing the primary.




More specifically:




The user should not be able to connect to the primary replica, only secondary.




In this case, it's not possible to do what you're wanting. You can't use read only routing with this as the first step in read only routing is to connect to the primary to check if the requirements to meet read only routing are correctly used and then get the metadata from the primary to understand where the new connection should take place.



You can, however, use something such as a network load balance appliance to dynamically update a cname or A record (AAAA if IPv6) to always point to a secondary. This would be specific to the load balancing software/hardware you choose to use. You could also write your own with a trivial amount of work.







share|improve this answer












share|improve this answer



share|improve this answer










answered 4 hours ago









Sean GallardySean Gallardy

16.7k22654




16.7k22654












  • I think you cleared this up, but please let me confirm. Reading the information I previously found there is obscurity in if a listener is used. In my scenario I can still connect to the secondary directly using the disabled login approach, but they would not benefit from the routing features of the AG. If I want to use the listener then the login needs to exist and be enabled on both. Does this sound right?

    – Dustin Laine
    3 hours ago











  • @DustinLaine Correct (disabled login on the primary)!

    – Sean Gallardy
    2 hours ago

















  • I think you cleared this up, but please let me confirm. Reading the information I previously found there is obscurity in if a listener is used. In my scenario I can still connect to the secondary directly using the disabled login approach, but they would not benefit from the routing features of the AG. If I want to use the listener then the login needs to exist and be enabled on both. Does this sound right?

    – Dustin Laine
    3 hours ago











  • @DustinLaine Correct (disabled login on the primary)!

    – Sean Gallardy
    2 hours ago
















I think you cleared this up, but please let me confirm. Reading the information I previously found there is obscurity in if a listener is used. In my scenario I can still connect to the secondary directly using the disabled login approach, but they would not benefit from the routing features of the AG. If I want to use the listener then the login needs to exist and be enabled on both. Does this sound right?

– Dustin Laine
3 hours ago





I think you cleared this up, but please let me confirm. Reading the information I previously found there is obscurity in if a listener is used. In my scenario I can still connect to the secondary directly using the disabled login approach, but they would not benefit from the routing features of the AG. If I want to use the listener then the login needs to exist and be enabled on both. Does this sound right?

– Dustin Laine
3 hours ago













@DustinLaine Correct (disabled login on the primary)!

– Sean Gallardy
2 hours ago





@DustinLaine Correct (disabled login on the primary)!

– Sean Gallardy
2 hours ago

















draft saved

draft discarded
















































Thanks for contributing an answer to Database Administrators Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f232174%2fsql-server-primary-login-restrictions%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Identifying “long and narrow” polygons in with PostGISlength and width of polygonWhy postgis st_overlaps reports Qgis' “avoid intersections” generated polygon as overlapping with others?Adjusting polygons to boundary and filling holesDrawing polygons with fixed area?How to remove spikes in Polygons with PostGISDeleting sliver polygons after difference operation in QGIS?Snapping boundaries in PostGISSplit polygon into parts adding attributes based on underlying polygon in QGISSplitting overlap between polygons and assign to nearest polygon using PostGIS?Expanding polygons and clipping at midpoint?Removing Intersection of Buffers in Same Layers

Masuk log Menu navigasi

อาณาจักร (ชีววิทยา) ดูเพิ่ม อ้างอิง รายการเลือกการนำทาง10.1086/39456810.5962/bhl.title.447410.1126/science.163.3863.150576276010.1007/BF01796092408502"Phylogenetic structure of the prokaryotic domain: the primary kingdoms"10.1073/pnas.74.11.5088432104270744"Towards a natural system of organisms: proposal for the domains Archaea, Bacteria, and Eucarya"1990PNAS...87.4576W10.1073/pnas.87.12.4576541592112744PubMedJump the queueexpand by handPubMedJump the queueexpand by handPubMedJump the queueexpand by hand"A revised six-kingdom system of life"10.1111/j.1469-185X.1998.tb00030.x9809012"Only six kingdoms of life"10.1098/rspb.2004.2705169172415306349"Kingdoms Protozoa and Chromista and the eozoan root of the eukaryotic tree"10.1098/rsbl.2009.0948288006020031978เพิ่มข้อมูล