tempdb log file full when executing SQL stored procedure from Crystal Reports 10

  • Hello, I have a problem when running a report in Crystal Reports 10 with an OLE DB connection to SQL Server 2000. The report executes a SQL stored procedure creating a large temporary table (30,000 rows), aggregates are then calculated from this large table and collected in a smaller summary temporary table using INSERT INTO.

    The report crashes in Crystal 10 with the error message : 'The log file for database 'tempdb' is full. Back up the transaction log for the database to free up some log space'. I used BACKUP LOG WITH TRUNCATE_ONLY to shrink the log file but the error still occurs.

    The stored procedure can be executed within SQL Query Analyzer with no error messages, which is curious as Crystal cannot execute the procedure without log file problems occuring.

    Can anyone offer a suggestion or view on this problem ?  Thanks

     

  • you can free the space where the tempdb placed.

  • I am not sure what Crystal Reports would be doing differently, but it is possible that it is handling it slightly differently from Query Analyzer.

    I have 2 suggestions that you may could check.

    1.  Check the backup mode of the Temp database.  Usually Tempdb's are in simple (SQL2000) or truncate on checkpoint(SQL7) which is probably what you want.  If it is in full(2000) or the truncate on checkpoint is not checked(7) you may want to try changing this. Since this would allow the Transaction log to truncate each time a commit occurs.

    2.  Add available space.  If you have an upper limit on the growth of the tempdb log file expand it.  If it is filling up the drive when you get this error, try to clean up some additional space on the drive, so that it has more room to grow.   

    Hope this helps.

    TJP8

  • Thanks for the advice, I am going to check the log file growth and backup mode

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

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