How can the tempdb transaction log be full?

  • When trying to export data from a table to a flat text file, I am suddenly encountering a failure, with the error message stating that the transaction log of tempdb is full and it needs to be backed up.

    I'm using the DTS wizard to create the export, the data is being pulled from one table, and there are approx 1M records being sent to the flat file.

    Earlier today - I was able to do the exact same process for approx 9M records, and it worked just fine.

    Can anyone help me identify what the trouble really is? I find it highly doubtful my tempdb transaction log is truly full - the size is fine. I have tried shrinkdatabase, just to be sure the log file has space, yet afterwards, I still get the same error.

    Any help is appreciated!

     

  • How big is the phsical TEMPDB log file?

    Is it set to autogrow?

     

  • Yes its set to autogrow, and has unlimited growth. Its currently has an available size of 50mb.

    Thanks!

  • How many Mb does 9 Million records represent?

    If you run the following query

    SELECT SUM(Length)

    FROM SysColumns

    WHERE ID=Object_Id('dbo.<<your table name>>')

    You will get a very crude idea of your record length.

    Multiply this by 9 Million and add 50% to the resulting figure.  That is probably a good starting point for your TempDB size.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply