Post reply

Avoiding updates from getting into log

  • November 5, 2007 at 4:04 am

    #73850

    Hi ,

    I have a database where I will be updating 500,000 daily rows in recent future. Is there anyway (other than truncating the log later) that can be used to avoid these updates from getting into transaction log? Or if I have to truncate the log later can I truncate only the portion where these updates will be logged?

    Thanks in advance.:)

    Regards,

    Rohit

  • November 5, 2007 at 5:14 am

    #748183

    Rohit Chitre (11/5/2007)

    Hi ,

    I have a database where I will be updating 500,000 daily rows in recent future. Is there anyway (other than truncating the log later) that can be used to avoid these updates from getting into transaction log? Or if I have to truncate the log later can I truncate only the portion where these updates will be logged?

    Thanks in advance.:)

    Regards,

    Rohit

    Unfortunately you can't just shrink a portion of the log. The only option is to use a BULK INSERT (select into) command for such operations. In this case you should switch your database into bulk-logged recovery model. All transactional log backups (if persist) containing such commands will fail.

  • November 5, 2007 at 5:36 am

    #748190

    Thanks for your reply. Is there anything that can be used for bulk updates?

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

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