Avoiding a full re-initialization when making changes to transactional replication












1















When I use the GUI to make any changes to transactional replication on SQL server, I live in fear of the "the changes you have made require a reinitialization of all articles" dialog.



I have had this happen even when doing something simple like adding or removing individual tables.



How do I avoid this?



Are there replication settings that impact when a full reinitialization is required? I found this blog post that claims that publication properties @immediate_sync and @allow_anonymous should be set to 0, I've done that but I've still sometimes had it prompt to reinitialize the whole thing.



Should I be scripting the add/remove instead of using the GUI?



Also, we frequently remove a table from replication but need to add it back in later, are there scripts out there to preserve the replication settings so this process is easier?










share|improve this question
















bumped to the homepage by Community 4 mins ago


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
















  • Still doesn't entirely answer the question of WHY?, but I found a similar post here: dba.stackexchange.com/a/57630/157

    – BradC
    Apr 28 '16 at 15:51
















1















When I use the GUI to make any changes to transactional replication on SQL server, I live in fear of the "the changes you have made require a reinitialization of all articles" dialog.



I have had this happen even when doing something simple like adding or removing individual tables.



How do I avoid this?



Are there replication settings that impact when a full reinitialization is required? I found this blog post that claims that publication properties @immediate_sync and @allow_anonymous should be set to 0, I've done that but I've still sometimes had it prompt to reinitialize the whole thing.



Should I be scripting the add/remove instead of using the GUI?



Also, we frequently remove a table from replication but need to add it back in later, are there scripts out there to preserve the replication settings so this process is easier?










share|improve this question
















bumped to the homepage by Community 4 mins ago


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
















  • Still doesn't entirely answer the question of WHY?, but I found a similar post here: dba.stackexchange.com/a/57630/157

    – BradC
    Apr 28 '16 at 15:51














1












1








1








When I use the GUI to make any changes to transactional replication on SQL server, I live in fear of the "the changes you have made require a reinitialization of all articles" dialog.



I have had this happen even when doing something simple like adding or removing individual tables.



How do I avoid this?



Are there replication settings that impact when a full reinitialization is required? I found this blog post that claims that publication properties @immediate_sync and @allow_anonymous should be set to 0, I've done that but I've still sometimes had it prompt to reinitialize the whole thing.



Should I be scripting the add/remove instead of using the GUI?



Also, we frequently remove a table from replication but need to add it back in later, are there scripts out there to preserve the replication settings so this process is easier?










share|improve this question
















When I use the GUI to make any changes to transactional replication on SQL server, I live in fear of the "the changes you have made require a reinitialization of all articles" dialog.



I have had this happen even when doing something simple like adding or removing individual tables.



How do I avoid this?



Are there replication settings that impact when a full reinitialization is required? I found this blog post that claims that publication properties @immediate_sync and @allow_anonymous should be set to 0, I've done that but I've still sometimes had it prompt to reinitialize the whole thing.



Should I be scripting the add/remove instead of using the GUI?



Also, we frequently remove a table from replication but need to add it back in later, are there scripts out there to preserve the replication settings so this process is easier?







sql-server replication






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 28 '16 at 15:38







BradC

















asked Apr 28 '16 at 15:07









BradCBradC

6,44063460




6,44063460





bumped to the homepage by Community 4 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 4 mins ago


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















  • Still doesn't entirely answer the question of WHY?, but I found a similar post here: dba.stackexchange.com/a/57630/157

    – BradC
    Apr 28 '16 at 15:51



















  • Still doesn't entirely answer the question of WHY?, but I found a similar post here: dba.stackexchange.com/a/57630/157

    – BradC
    Apr 28 '16 at 15:51

















Still doesn't entirely answer the question of WHY?, but I found a similar post here: dba.stackexchange.com/a/57630/157

– BradC
Apr 28 '16 at 15:51





Still doesn't entirely answer the question of WHY?, but I found a similar post here: dba.stackexchange.com/a/57630/157

– BradC
Apr 28 '16 at 15:51










1 Answer
1






active

oldest

votes


















0















I've done that but I've still sometimes had it prompt to reinitialize the whole thing.




The snapshot will only contain the new table that has been added.




Also, we frequently remove a table from replication but need to add it back in later, are there scripts out there to preserve the replication settings so this process is easier?




Script out replication - right click - script to file. Change the parameters @immediate_sync and @allow_anonymous should be set to 0.



Run the script post completion of your work.



Also, check my answer for Transactional replication altering tables and adding stored procedures that will help when you are adding columns to existing replication.






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%2f136866%2favoiding-a-full-re-initialization-when-making-changes-to-transactional-replicati%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















    I've done that but I've still sometimes had it prompt to reinitialize the whole thing.




    The snapshot will only contain the new table that has been added.




    Also, we frequently remove a table from replication but need to add it back in later, are there scripts out there to preserve the replication settings so this process is easier?




    Script out replication - right click - script to file. Change the parameters @immediate_sync and @allow_anonymous should be set to 0.



    Run the script post completion of your work.



    Also, check my answer for Transactional replication altering tables and adding stored procedures that will help when you are adding columns to existing replication.






    share|improve this answer






























      0















      I've done that but I've still sometimes had it prompt to reinitialize the whole thing.




      The snapshot will only contain the new table that has been added.




      Also, we frequently remove a table from replication but need to add it back in later, are there scripts out there to preserve the replication settings so this process is easier?




      Script out replication - right click - script to file. Change the parameters @immediate_sync and @allow_anonymous should be set to 0.



      Run the script post completion of your work.



      Also, check my answer for Transactional replication altering tables and adding stored procedures that will help when you are adding columns to existing replication.






      share|improve this answer




























        0












        0








        0








        I've done that but I've still sometimes had it prompt to reinitialize the whole thing.




        The snapshot will only contain the new table that has been added.




        Also, we frequently remove a table from replication but need to add it back in later, are there scripts out there to preserve the replication settings so this process is easier?




        Script out replication - right click - script to file. Change the parameters @immediate_sync and @allow_anonymous should be set to 0.



        Run the script post completion of your work.



        Also, check my answer for Transactional replication altering tables and adding stored procedures that will help when you are adding columns to existing replication.






        share|improve this answer
















        I've done that but I've still sometimes had it prompt to reinitialize the whole thing.




        The snapshot will only contain the new table that has been added.




        Also, we frequently remove a table from replication but need to add it back in later, are there scripts out there to preserve the replication settings so this process is easier?




        Script out replication - right click - script to file. Change the parameters @immediate_sync and @allow_anonymous should be set to 0.



        Run the script post completion of your work.



        Also, check my answer for Transactional replication altering tables and adding stored procedures that will help when you are adding columns to existing replication.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Apr 13 '17 at 12:43









        Community

        1




        1










        answered Apr 28 '16 at 15:51









        KinKin

        53.6k481190




        53.6k481190






























            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%2f136866%2favoiding-a-full-re-initialization-when-making-changes-to-transactional-replicati%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