Trace Flag impact to Mirrored Databases












1















I want to enable dead lock trace flag -t1222 on a production SQL Server 2014 instance. Many databases on this instance are configured with database mirroring. What (if any) impact to mirrored databases will occur after applying -t1222 and restarting the server?










share|improve this question




















  • 3





    Why not use extended events to track the deadlocks instead?

    – vonPryz
    Dec 12 '18 at 8:50
















1















I want to enable dead lock trace flag -t1222 on a production SQL Server 2014 instance. Many databases on this instance are configured with database mirroring. What (if any) impact to mirrored databases will occur after applying -t1222 and restarting the server?










share|improve this question




















  • 3





    Why not use extended events to track the deadlocks instead?

    – vonPryz
    Dec 12 '18 at 8:50














1












1








1








I want to enable dead lock trace flag -t1222 on a production SQL Server 2014 instance. Many databases on this instance are configured with database mirroring. What (if any) impact to mirrored databases will occur after applying -t1222 and restarting the server?










share|improve this question
















I want to enable dead lock trace flag -t1222 on a production SQL Server 2014 instance. Many databases on this instance are configured with database mirroring. What (if any) impact to mirrored databases will occur after applying -t1222 and restarting the server?







sql-server sql-server-2014 mirroring trace-flags






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 12 '18 at 8:52









Tom V

13.8k74677




13.8k74677










asked Dec 12 '18 at 7:09









Nasar Babu ChowdaryNasar Babu Chowdary

113




113








  • 3





    Why not use extended events to track the deadlocks instead?

    – vonPryz
    Dec 12 '18 at 8:50














  • 3





    Why not use extended events to track the deadlocks instead?

    – vonPryz
    Dec 12 '18 at 8:50








3




3





Why not use extended events to track the deadlocks instead?

– vonPryz
Dec 12 '18 at 8:50





Why not use extended events to track the deadlocks instead?

– vonPryz
Dec 12 '18 at 8:50










1 Answer
1






active

oldest

votes


















4















What (if any) impact to mirrored databases will occur after applying -t1222 and restarting the server?




Since 1222 writes deadlock information to the log, the impact to mirroring itself will be nothing. Secondary effects should also be intangible in a normal environment. I'd only be worried if, for some reason, you have so many deadlocks that the Errorlog ends up filling your drive as this is fairly benign.



Also, by default, the extended events session does track deadlock information but it may not have all of the deadlock graph given the size of the deadlock graph.






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%2f224725%2ftrace-flag-impact-to-mirrored-databases%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









    4















    What (if any) impact to mirrored databases will occur after applying -t1222 and restarting the server?




    Since 1222 writes deadlock information to the log, the impact to mirroring itself will be nothing. Secondary effects should also be intangible in a normal environment. I'd only be worried if, for some reason, you have so many deadlocks that the Errorlog ends up filling your drive as this is fairly benign.



    Also, by default, the extended events session does track deadlock information but it may not have all of the deadlock graph given the size of the deadlock graph.






    share|improve this answer




























      4















      What (if any) impact to mirrored databases will occur after applying -t1222 and restarting the server?




      Since 1222 writes deadlock information to the log, the impact to mirroring itself will be nothing. Secondary effects should also be intangible in a normal environment. I'd only be worried if, for some reason, you have so many deadlocks that the Errorlog ends up filling your drive as this is fairly benign.



      Also, by default, the extended events session does track deadlock information but it may not have all of the deadlock graph given the size of the deadlock graph.






      share|improve this answer


























        4












        4








        4








        What (if any) impact to mirrored databases will occur after applying -t1222 and restarting the server?




        Since 1222 writes deadlock information to the log, the impact to mirroring itself will be nothing. Secondary effects should also be intangible in a normal environment. I'd only be worried if, for some reason, you have so many deadlocks that the Errorlog ends up filling your drive as this is fairly benign.



        Also, by default, the extended events session does track deadlock information but it may not have all of the deadlock graph given the size of the deadlock graph.






        share|improve this answer














        What (if any) impact to mirrored databases will occur after applying -t1222 and restarting the server?




        Since 1222 writes deadlock information to the log, the impact to mirroring itself will be nothing. Secondary effects should also be intangible in a normal environment. I'd only be worried if, for some reason, you have so many deadlocks that the Errorlog ends up filling your drive as this is fairly benign.



        Also, by default, the extended events session does track deadlock information but it may not have all of the deadlock graph given the size of the deadlock graph.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Dec 12 '18 at 11:35









        Sean GallardySean Gallardy

        15.8k22548




        15.8k22548






























            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%2f224725%2ftrace-flag-impact-to-mirrored-databases%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

            How do I know what Microsoft account the skydrive app is syncing to?

            When does type information flow backwards in C++?

            Grease: Live!