IBM DB2 Timetravel logging based on some criteria












0















I have been searching for the condition, where, lets say when we enable time travel to a certain table in DB2 , but don't want to capture all the updates done, but only the updates that's done by some specific user.



Wanted to know if this is at all possible with the DB2 time travel and how we can achieve it .










share|improve this question


















  • 1





    I'm voting to close this question as off-topic because it's cross-posted on dba.stackexchange.com/questions/223209/…

    – mustaccio
    Nov 22 '18 at 13:59
















0















I have been searching for the condition, where, lets say when we enable time travel to a certain table in DB2 , but don't want to capture all the updates done, but only the updates that's done by some specific user.



Wanted to know if this is at all possible with the DB2 time travel and how we can achieve it .










share|improve this question


















  • 1





    I'm voting to close this question as off-topic because it's cross-posted on dba.stackexchange.com/questions/223209/…

    – mustaccio
    Nov 22 '18 at 13:59














0












0








0








I have been searching for the condition, where, lets say when we enable time travel to a certain table in DB2 , but don't want to capture all the updates done, but only the updates that's done by some specific user.



Wanted to know if this is at all possible with the DB2 time travel and how we can achieve it .










share|improve this question














I have been searching for the condition, where, lets say when we enable time travel to a certain table in DB2 , but don't want to capture all the updates done, but only the updates that's done by some specific user.



Wanted to know if this is at all possible with the DB2 time travel and how we can achieve it .







db2 temporal-database






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 22 '18 at 13:37









Yogesh ChavanYogesh Chavan

126




126








  • 1





    I'm voting to close this question as off-topic because it's cross-posted on dba.stackexchange.com/questions/223209/…

    – mustaccio
    Nov 22 '18 at 13:59














  • 1





    I'm voting to close this question as off-topic because it's cross-posted on dba.stackexchange.com/questions/223209/…

    – mustaccio
    Nov 22 '18 at 13:59








1




1





I'm voting to close this question as off-topic because it's cross-posted on dba.stackexchange.com/questions/223209/…

– mustaccio
Nov 22 '18 at 13:59





I'm voting to close this question as off-topic because it's cross-posted on dba.stackexchange.com/questions/223209/…

– mustaccio
Nov 22 '18 at 13:59












2 Answers
2






active

oldest

votes


















0














It's not possible with DB2 temporal tables.






share|improve this answer
























  • the SET_MAINT_MODE_RECORD_NO_TEMPORALHISTORY procedure can be used to disable recording system time changes for the duration of your session

    – Paul Vernon
    Nov 23 '18 at 14:58











  • Well, such a call may be used theoretically in, let's say, a connection procedure, where it might be called for all other users except the one need. But I believe, that it's some improper use of temporal tables. It's better to use triggers.

    – Mark Barinstein
    Nov 23 '18 at 19:22





















0














Alter the temporal table add a user column maintained by system.
db2 for Iseries column shown



EMP_CHANGE_USER VARCHAR(18) GENERATED ALWAYS AS (USER)


The new column will go automatically to the history table of the temporal table. You can report on the history table and have emp_change user.



Note: IRL Don't single out users. You can give management a report that lists out all users and management can filter it down to individuals. Programmers do not single out users for reporting and logging.






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    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: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    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%2fstackoverflow.com%2fquestions%2f53432230%2fibm-db2-timetravel-logging-based-on-some-criteria%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    It's not possible with DB2 temporal tables.






    share|improve this answer
























    • the SET_MAINT_MODE_RECORD_NO_TEMPORALHISTORY procedure can be used to disable recording system time changes for the duration of your session

      – Paul Vernon
      Nov 23 '18 at 14:58











    • Well, such a call may be used theoretically in, let's say, a connection procedure, where it might be called for all other users except the one need. But I believe, that it's some improper use of temporal tables. It's better to use triggers.

      – Mark Barinstein
      Nov 23 '18 at 19:22


















    0














    It's not possible with DB2 temporal tables.






    share|improve this answer
























    • the SET_MAINT_MODE_RECORD_NO_TEMPORALHISTORY procedure can be used to disable recording system time changes for the duration of your session

      – Paul Vernon
      Nov 23 '18 at 14:58











    • Well, such a call may be used theoretically in, let's say, a connection procedure, where it might be called for all other users except the one need. But I believe, that it's some improper use of temporal tables. It's better to use triggers.

      – Mark Barinstein
      Nov 23 '18 at 19:22
















    0












    0








    0







    It's not possible with DB2 temporal tables.






    share|improve this answer













    It's not possible with DB2 temporal tables.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Nov 22 '18 at 13:47









    Mark BarinsteinMark Barinstein

    1,896124




    1,896124













    • the SET_MAINT_MODE_RECORD_NO_TEMPORALHISTORY procedure can be used to disable recording system time changes for the duration of your session

      – Paul Vernon
      Nov 23 '18 at 14:58











    • Well, such a call may be used theoretically in, let's say, a connection procedure, where it might be called for all other users except the one need. But I believe, that it's some improper use of temporal tables. It's better to use triggers.

      – Mark Barinstein
      Nov 23 '18 at 19:22





















    • the SET_MAINT_MODE_RECORD_NO_TEMPORALHISTORY procedure can be used to disable recording system time changes for the duration of your session

      – Paul Vernon
      Nov 23 '18 at 14:58











    • Well, such a call may be used theoretically in, let's say, a connection procedure, where it might be called for all other users except the one need. But I believe, that it's some improper use of temporal tables. It's better to use triggers.

      – Mark Barinstein
      Nov 23 '18 at 19:22



















    the SET_MAINT_MODE_RECORD_NO_TEMPORALHISTORY procedure can be used to disable recording system time changes for the duration of your session

    – Paul Vernon
    Nov 23 '18 at 14:58





    the SET_MAINT_MODE_RECORD_NO_TEMPORALHISTORY procedure can be used to disable recording system time changes for the duration of your session

    – Paul Vernon
    Nov 23 '18 at 14:58













    Well, such a call may be used theoretically in, let's say, a connection procedure, where it might be called for all other users except the one need. But I believe, that it's some improper use of temporal tables. It's better to use triggers.

    – Mark Barinstein
    Nov 23 '18 at 19:22







    Well, such a call may be used theoretically in, let's say, a connection procedure, where it might be called for all other users except the one need. But I believe, that it's some improper use of temporal tables. It's better to use triggers.

    – Mark Barinstein
    Nov 23 '18 at 19:22















    0














    Alter the temporal table add a user column maintained by system.
    db2 for Iseries column shown



    EMP_CHANGE_USER VARCHAR(18) GENERATED ALWAYS AS (USER)


    The new column will go automatically to the history table of the temporal table. You can report on the history table and have emp_change user.



    Note: IRL Don't single out users. You can give management a report that lists out all users and management can filter it down to individuals. Programmers do not single out users for reporting and logging.






    share|improve this answer




























      0














      Alter the temporal table add a user column maintained by system.
      db2 for Iseries column shown



      EMP_CHANGE_USER VARCHAR(18) GENERATED ALWAYS AS (USER)


      The new column will go automatically to the history table of the temporal table. You can report on the history table and have emp_change user.



      Note: IRL Don't single out users. You can give management a report that lists out all users and management can filter it down to individuals. Programmers do not single out users for reporting and logging.






      share|improve this answer


























        0












        0








        0







        Alter the temporal table add a user column maintained by system.
        db2 for Iseries column shown



        EMP_CHANGE_USER VARCHAR(18) GENERATED ALWAYS AS (USER)


        The new column will go automatically to the history table of the temporal table. You can report on the history table and have emp_change user.



        Note: IRL Don't single out users. You can give management a report that lists out all users and management can filter it down to individuals. Programmers do not single out users for reporting and logging.






        share|improve this answer













        Alter the temporal table add a user column maintained by system.
        db2 for Iseries column shown



        EMP_CHANGE_USER VARCHAR(18) GENERATED ALWAYS AS (USER)


        The new column will go automatically to the history table of the temporal table. You can report on the history table and have emp_change user.



        Note: IRL Don't single out users. You can give management a report that lists out all users and management can filter it down to individuals. Programmers do not single out users for reporting and logging.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 23 '18 at 17:03









        danny117danny117

        5,14111933




        5,14111933






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • 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%2fstackoverflow.com%2fquestions%2f53432230%2fibm-db2-timetravel-logging-based-on-some-criteria%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

            "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

            Alcedinidae

            RAC Tourist Trophy