“The transaction log for database 'tempdb' is full due to 'ACTIVE_TRANSACTION'.” after adding indexes to...





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






up vote
1
down vote

favorite












Recently, I added some indexes on temp tables to procedures which prepare data for data warehouse. On a testing db, tests of these procedures worked fine but when running on client's server it failed due to this error and the server needed to be restarted. Can this be related to adding the indexes or it could be something totally else?



Client's server version:




  • Microsoft SQL Server 2014 (SP3) (KB4022619) - 12.0.6024.0 (X64)
    Enterprise Edition (64-bit) on Windows NT 6.3 (Build 9600: ) (Hypervisor)


Testing server version:




  • Microsoft SQL Server 2014 - 12.0.4100.1 (X64) Developer Edition (64-bit) on Windows NT 6.3 (Build 9600: ) (Hypervisor)










share|improve this question









New contributor




jindrich is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • Yes, it can be. Add details about servers versions into your question.
    – Denis Rubashkin
    Nov 13 at 13:24






  • 1




    jindrich, check how how to merge accounts as it appears you have 2 different ones you're attempting to use.
    – LowlyDBA
    Nov 13 at 14:28










  • You can run DBCC OPENTRAN and see what's going on.
    – Terry Carmen
    Nov 13 at 18:18

















up vote
1
down vote

favorite












Recently, I added some indexes on temp tables to procedures which prepare data for data warehouse. On a testing db, tests of these procedures worked fine but when running on client's server it failed due to this error and the server needed to be restarted. Can this be related to adding the indexes or it could be something totally else?



Client's server version:




  • Microsoft SQL Server 2014 (SP3) (KB4022619) - 12.0.6024.0 (X64)
    Enterprise Edition (64-bit) on Windows NT 6.3 (Build 9600: ) (Hypervisor)


Testing server version:




  • Microsoft SQL Server 2014 - 12.0.4100.1 (X64) Developer Edition (64-bit) on Windows NT 6.3 (Build 9600: ) (Hypervisor)










share|improve this question









New contributor




jindrich is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • Yes, it can be. Add details about servers versions into your question.
    – Denis Rubashkin
    Nov 13 at 13:24






  • 1




    jindrich, check how how to merge accounts as it appears you have 2 different ones you're attempting to use.
    – LowlyDBA
    Nov 13 at 14:28










  • You can run DBCC OPENTRAN and see what's going on.
    – Terry Carmen
    Nov 13 at 18:18













up vote
1
down vote

favorite









up vote
1
down vote

favorite











Recently, I added some indexes on temp tables to procedures which prepare data for data warehouse. On a testing db, tests of these procedures worked fine but when running on client's server it failed due to this error and the server needed to be restarted. Can this be related to adding the indexes or it could be something totally else?



Client's server version:




  • Microsoft SQL Server 2014 (SP3) (KB4022619) - 12.0.6024.0 (X64)
    Enterprise Edition (64-bit) on Windows NT 6.3 (Build 9600: ) (Hypervisor)


Testing server version:




  • Microsoft SQL Server 2014 - 12.0.4100.1 (X64) Developer Edition (64-bit) on Windows NT 6.3 (Build 9600: ) (Hypervisor)










share|improve this question









New contributor




jindrich is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











Recently, I added some indexes on temp tables to procedures which prepare data for data warehouse. On a testing db, tests of these procedures worked fine but when running on client's server it failed due to this error and the server needed to be restarted. Can this be related to adding the indexes or it could be something totally else?



Client's server version:




  • Microsoft SQL Server 2014 (SP3) (KB4022619) - 12.0.6024.0 (X64)
    Enterprise Edition (64-bit) on Windows NT 6.3 (Build 9600: ) (Hypervisor)


Testing server version:




  • Microsoft SQL Server 2014 - 12.0.4100.1 (X64) Developer Edition (64-bit) on Windows NT 6.3 (Build 9600: ) (Hypervisor)







sql-server index sql-server-2014 tempdb temporary-tables






share|improve this question









New contributor




jindrich is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




jindrich is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited Nov 13 at 15:30









LowlyDBA

6,66352241




6,66352241






New contributor




jindrich is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked Nov 13 at 13:15









jindrich

61




61




New contributor




jindrich is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





jindrich is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






jindrich is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












  • Yes, it can be. Add details about servers versions into your question.
    – Denis Rubashkin
    Nov 13 at 13:24






  • 1




    jindrich, check how how to merge accounts as it appears you have 2 different ones you're attempting to use.
    – LowlyDBA
    Nov 13 at 14:28










  • You can run DBCC OPENTRAN and see what's going on.
    – Terry Carmen
    Nov 13 at 18:18


















  • Yes, it can be. Add details about servers versions into your question.
    – Denis Rubashkin
    Nov 13 at 13:24






  • 1




    jindrich, check how how to merge accounts as it appears you have 2 different ones you're attempting to use.
    – LowlyDBA
    Nov 13 at 14:28










  • You can run DBCC OPENTRAN and see what's going on.
    – Terry Carmen
    Nov 13 at 18:18
















Yes, it can be. Add details about servers versions into your question.
– Denis Rubashkin
Nov 13 at 13:24




Yes, it can be. Add details about servers versions into your question.
– Denis Rubashkin
Nov 13 at 13:24




1




1




jindrich, check how how to merge accounts as it appears you have 2 different ones you're attempting to use.
– LowlyDBA
Nov 13 at 14:28




jindrich, check how how to merge accounts as it appears you have 2 different ones you're attempting to use.
– LowlyDBA
Nov 13 at 14:28












You can run DBCC OPENTRAN and see what's going on.
– Terry Carmen
Nov 13 at 18:18




You can run DBCC OPENTRAN and see what's going on.
– Terry Carmen
Nov 13 at 18:18










1 Answer
1






active

oldest

votes

















up vote
5
down vote













An index create on a temp table will use space in the tempdb transaction log while the index is being built. So yes, the index could have caused the issue in the general sense that it added enough transactions to the log file that it ran out of space.



Transaction Log Disk Space for Index Operations






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: 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
    });


    }
    });






    jindrich is a new contributor. Be nice, and check out our Code of Conduct.










     

    draft saved


    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f222429%2fthe-transaction-log-for-database-tempdb-is-full-due-to-active-transaction%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








    up vote
    5
    down vote













    An index create on a temp table will use space in the tempdb transaction log while the index is being built. So yes, the index could have caused the issue in the general sense that it added enough transactions to the log file that it ran out of space.



    Transaction Log Disk Space for Index Operations






    share|improve this answer

























      up vote
      5
      down vote













      An index create on a temp table will use space in the tempdb transaction log while the index is being built. So yes, the index could have caused the issue in the general sense that it added enough transactions to the log file that it ran out of space.



      Transaction Log Disk Space for Index Operations






      share|improve this answer























        up vote
        5
        down vote










        up vote
        5
        down vote









        An index create on a temp table will use space in the tempdb transaction log while the index is being built. So yes, the index could have caused the issue in the general sense that it added enough transactions to the log file that it ran out of space.



        Transaction Log Disk Space for Index Operations






        share|improve this answer












        An index create on a temp table will use space in the tempdb transaction log while the index is being built. So yes, the index could have caused the issue in the general sense that it added enough transactions to the log file that it ran out of space.



        Transaction Log Disk Space for Index Operations







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 13 at 13:32









        Tony Hinkle

        1,5241417




        1,5241417






















            jindrich is a new contributor. Be nice, and check out our Code of Conduct.










             

            draft saved


            draft discarded


















            jindrich is a new contributor. Be nice, and check out our Code of Conduct.













            jindrich is a new contributor. Be nice, and check out our Code of Conduct.












            jindrich is a new contributor. Be nice, and check out our Code of Conduct.















             


            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f222429%2fthe-transaction-log-for-database-tempdb-is-full-due-to-active-transaction%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!