Post reply

Will using a Temp table as working / staging tables reduce the log backup size?

  • July 23, 2013 at 9:22 pm

    #280713

    I just want to clarify something.

    I am trying to reduce the size of the log file backups created by certain processes at certain times of the day.

    I understand logging will and should occur but:

    If a process inserts, updates etc data in TEMPDB Temp tables for staging then I assume although this data is logged to the tempdb log file it will not get back up (presumably because the TEMPDB log file is not backed up!).

    So my question is: If I get a user that is creating large log files using normal tables as working / staging tables, therefore large log file backups -- can I reduce this by requesting working / staging data be done in TEMPDB temporary tables?

    thanks

  • July 24, 2013 at 4:12 am

    #1635273

    rather than put more work on the tempDb, you could create them a dedicated Staging Database and put this in simple mode so that log backups are not needed.

  • July 24, 2013 at 5:02 am

    #1635292

    Are they inserting data into the regular tables and then updating it in place as part of a single operation?

    If so, your approach could possibly work. But what about just eliminating the secondary update process. Figure out all the data and make it a single batch process instead of multi-pass operations?

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • July 24, 2013 at 1:46 pm

    #1635509

    rather than put more work on the tempDb, you could create them a dedicated Staging Database and put this in simple mode so that log backups are not needed.

    Yes that is a good idea and would probably work

    If so, your approach could possibly work. But what about just eliminating the secondary update process. Figure out all the data and make it a single batch process instead of multi-pass operations?

    The process is quite complex from a business perspective ie working out loyalty points expiry for various periods and tiers.

    So although it may be able to be done in a single batch I guess it has been broken down into many staging tables for debugging / checking reasons.

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

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