Availability groups and Linked Servers

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
1
down vote

favorite












I have inherited an Availability Group and have found that a linked server was set up between the two nodes of the availability group. It is using sa for authentication unfortunately.



Simultaneously, some of the team's developers use sa to query the live DB. I want this to stop.



My question is:



Are linked servers in any way required by availability groups? I know I have some bespoke moving parts like Agent jobs that use the linked server to sync jobs between the two nodes. I'm more concerned about something internal to SQL Server that I might not be aware of. Anything wrong with just doing normal due diligence and changing the linked server user to use non-sa and also changing the sa password?










share|improve this question





























    up vote
    1
    down vote

    favorite












    I have inherited an Availability Group and have found that a linked server was set up between the two nodes of the availability group. It is using sa for authentication unfortunately.



    Simultaneously, some of the team's developers use sa to query the live DB. I want this to stop.



    My question is:



    Are linked servers in any way required by availability groups? I know I have some bespoke moving parts like Agent jobs that use the linked server to sync jobs between the two nodes. I'm more concerned about something internal to SQL Server that I might not be aware of. Anything wrong with just doing normal due diligence and changing the linked server user to use non-sa and also changing the sa password?










    share|improve this question

























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I have inherited an Availability Group and have found that a linked server was set up between the two nodes of the availability group. It is using sa for authentication unfortunately.



      Simultaneously, some of the team's developers use sa to query the live DB. I want this to stop.



      My question is:



      Are linked servers in any way required by availability groups? I know I have some bespoke moving parts like Agent jobs that use the linked server to sync jobs between the two nodes. I'm more concerned about something internal to SQL Server that I might not be aware of. Anything wrong with just doing normal due diligence and changing the linked server user to use non-sa and also changing the sa password?










      share|improve this question















      I have inherited an Availability Group and have found that a linked server was set up between the two nodes of the availability group. It is using sa for authentication unfortunately.



      Simultaneously, some of the team's developers use sa to query the live DB. I want this to stop.



      My question is:



      Are linked servers in any way required by availability groups? I know I have some bespoke moving parts like Agent jobs that use the linked server to sync jobs between the two nodes. I'm more concerned about something internal to SQL Server that I might not be aware of. Anything wrong with just doing normal due diligence and changing the linked server user to use non-sa and also changing the sa password?







      sql-server sql-server-2016 availability-groups linked-server






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 3 hours ago









      Shanky

      13.5k32039




      13.5k32039










      asked 4 hours ago









      Peter

      7261625




      7261625




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          3
          down vote














          Are linked servers in any way required by availability groups?




          Absolutely not needed by SQL Server for Availability Groups!




          Anything wrong with just doing normal due diligence and changing the linked server user to use non-sa and also changing the sa password?




          No, I agree with your approach as long as it doesn't break the business requirements. However, if the developers are using it to query around then I could argue that they should be changing their software to do this, rather than a linked server.



          I would tend to agree that it's most likely used to automagically sync logins and jobs, but again there is no need for an actual linked server to do this though I could see why they would use a highly privileged account so they wouldn't have to worry about permissions.






          share|improve this answer




















            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',
            convertImagesToLinks: false,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            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%2f220215%2favailability-groups-and-linked-servers%23new-answer', 'question_page');

            );

            Post as a guest






























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            3
            down vote














            Are linked servers in any way required by availability groups?




            Absolutely not needed by SQL Server for Availability Groups!




            Anything wrong with just doing normal due diligence and changing the linked server user to use non-sa and also changing the sa password?




            No, I agree with your approach as long as it doesn't break the business requirements. However, if the developers are using it to query around then I could argue that they should be changing their software to do this, rather than a linked server.



            I would tend to agree that it's most likely used to automagically sync logins and jobs, but again there is no need for an actual linked server to do this though I could see why they would use a highly privileged account so they wouldn't have to worry about permissions.






            share|improve this answer
























              up vote
              3
              down vote














              Are linked servers in any way required by availability groups?




              Absolutely not needed by SQL Server for Availability Groups!




              Anything wrong with just doing normal due diligence and changing the linked server user to use non-sa and also changing the sa password?




              No, I agree with your approach as long as it doesn't break the business requirements. However, if the developers are using it to query around then I could argue that they should be changing their software to do this, rather than a linked server.



              I would tend to agree that it's most likely used to automagically sync logins and jobs, but again there is no need for an actual linked server to do this though I could see why they would use a highly privileged account so they wouldn't have to worry about permissions.






              share|improve this answer






















                up vote
                3
                down vote










                up vote
                3
                down vote










                Are linked servers in any way required by availability groups?




                Absolutely not needed by SQL Server for Availability Groups!




                Anything wrong with just doing normal due diligence and changing the linked server user to use non-sa and also changing the sa password?




                No, I agree with your approach as long as it doesn't break the business requirements. However, if the developers are using it to query around then I could argue that they should be changing their software to do this, rather than a linked server.



                I would tend to agree that it's most likely used to automagically sync logins and jobs, but again there is no need for an actual linked server to do this though I could see why they would use a highly privileged account so they wouldn't have to worry about permissions.






                share|improve this answer













                Are linked servers in any way required by availability groups?




                Absolutely not needed by SQL Server for Availability Groups!




                Anything wrong with just doing normal due diligence and changing the linked server user to use non-sa and also changing the sa password?




                No, I agree with your approach as long as it doesn't break the business requirements. However, if the developers are using it to query around then I could argue that they should be changing their software to do this, rather than a linked server.



                I would tend to agree that it's most likely used to automagically sync logins and jobs, but again there is no need for an actual linked server to do this though I could see why they would use a highly privileged account so they wouldn't have to worry about permissions.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 3 hours ago









                Sean Gallardy

                13.6k11944




                13.6k11944



























                     

                    draft saved


                    draft discarded















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f220215%2favailability-groups-and-linked-servers%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Comments

                    Popular posts from this blog

                    What does second last employer means? [closed]

                    List of Gilmore Girls characters

                    Confectionery