How to remove a listener IP from a SQL Availability Group Listener by T-SQL












3















The title says it all.
I have an availability group that was a multiple subnet, but now the environment have changed ,all replicas exist within a single subnet.
How to remove the superfluous second IP.
Is this only way remove the ip from Failover Cluster Manager?
I have submited a feedback to micosoft,welcome to vote.



https://connect.microsoft.com/SQLServer/feedback/details/2907012/how-do-you-remove-a-listener-ip-from-a-sql-availability-group-listener










share|improve this question
















bumped to the homepage by Community 24 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    3















    The title says it all.
    I have an availability group that was a multiple subnet, but now the environment have changed ,all replicas exist within a single subnet.
    How to remove the superfluous second IP.
    Is this only way remove the ip from Failover Cluster Manager?
    I have submited a feedback to micosoft,welcome to vote.



    https://connect.microsoft.com/SQLServer/feedback/details/2907012/how-do-you-remove-a-listener-ip-from-a-sql-availability-group-listener










    share|improve this question
















    bumped to the homepage by Community 24 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      3












      3








      3








      The title says it all.
      I have an availability group that was a multiple subnet, but now the environment have changed ,all replicas exist within a single subnet.
      How to remove the superfluous second IP.
      Is this only way remove the ip from Failover Cluster Manager?
      I have submited a feedback to micosoft,welcome to vote.



      https://connect.microsoft.com/SQLServer/feedback/details/2907012/how-do-you-remove-a-listener-ip-from-a-sql-availability-group-listener










      share|improve this question
















      The title says it all.
      I have an availability group that was a multiple subnet, but now the environment have changed ,all replicas exist within a single subnet.
      How to remove the superfluous second IP.
      Is this only way remove the ip from Failover Cluster Manager?
      I have submited a feedback to micosoft,welcome to vote.



      https://connect.microsoft.com/SQLServer/feedback/details/2907012/how-do-you-remove-a-listener-ip-from-a-sql-availability-group-listener







      sql-server availability-groups






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jul 27 '17 at 18:30









      Max Vernon

      50.9k13112224




      50.9k13112224










      asked Jul 29 '16 at 5:15









      slade.liuslade.liu

      364




      364





      bumped to the homepage by Community 24 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 24 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Based on my experience with SQL Server 2014 and 2016, you can simply remove the IP address resource in Failover Cluster Administrator. We have done this on several non-production clusters and on a production cluster in order to move from one subnet to the other. I stopped the SQL Server service on all nodes to ensure that there would be no connections and less chance of some sort of conflict since it's a bit out of the ordinary.



          The other option is to simply take a few minutes of downtime to remove the listener and rebuild it. If you scripted all of the operations it should only take seconds.






          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',
            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%2f145297%2fhow-to-remove-a-listener-ip-from-a-sql-availability-group-listener-by-t-sql%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









            0














            Based on my experience with SQL Server 2014 and 2016, you can simply remove the IP address resource in Failover Cluster Administrator. We have done this on several non-production clusters and on a production cluster in order to move from one subnet to the other. I stopped the SQL Server service on all nodes to ensure that there would be no connections and less chance of some sort of conflict since it's a bit out of the ordinary.



            The other option is to simply take a few minutes of downtime to remove the listener and rebuild it. If you scripted all of the operations it should only take seconds.






            share|improve this answer




























              0














              Based on my experience with SQL Server 2014 and 2016, you can simply remove the IP address resource in Failover Cluster Administrator. We have done this on several non-production clusters and on a production cluster in order to move from one subnet to the other. I stopped the SQL Server service on all nodes to ensure that there would be no connections and less chance of some sort of conflict since it's a bit out of the ordinary.



              The other option is to simply take a few minutes of downtime to remove the listener and rebuild it. If you scripted all of the operations it should only take seconds.






              share|improve this answer


























                0












                0








                0







                Based on my experience with SQL Server 2014 and 2016, you can simply remove the IP address resource in Failover Cluster Administrator. We have done this on several non-production clusters and on a production cluster in order to move from one subnet to the other. I stopped the SQL Server service on all nodes to ensure that there would be no connections and less chance of some sort of conflict since it's a bit out of the ordinary.



                The other option is to simply take a few minutes of downtime to remove the listener and rebuild it. If you scripted all of the operations it should only take seconds.






                share|improve this answer













                Based on my experience with SQL Server 2014 and 2016, you can simply remove the IP address resource in Failover Cluster Administrator. We have done this on several non-production clusters and on a production cluster in order to move from one subnet to the other. I stopped the SQL Server service on all nodes to ensure that there would be no connections and less chance of some sort of conflict since it's a bit out of the ordinary.



                The other option is to simply take a few minutes of downtime to remove the listener and rebuild it. If you scripted all of the operations it should only take seconds.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 17 at 11:09









                Tony HinkleTony Hinkle

                2,7051423




                2,7051423






























                    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%2f145297%2fhow-to-remove-a-listener-ip-from-a-sql-availability-group-listener-by-t-sql%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

                    SQL Server 17 - Attemping to backup to remote NAS but Access is denied

                    Always On Availability groups resolving state after failover - Remote harden of transaction...

                    Restoring from pg_dump with foreign key constraints