Post reply

LS

  • July 18, 2013 at 12:23 am

    #296493

    what happens to the logshipping when we delete tuf file ?

  • July 18, 2013 at 12:30 am

    #1633532

    please explain: "tuf file"

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **

  • July 18, 2013 at 12:34 am

    #1633534

    .TUF -transaction undo file

  • July 18, 2013 at 12:37 am

    #1633535

    ramyours2003 (7/18/2013)

    .TUF -transaction undo file

    SQL Server doesn't have a Transaction Undo File. I think you are working with Oracle. This forum is about Micorosoft SQL Server. Very few posters will have extensive experience with Oracle.

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **

  • July 19, 2013 at 5:29 am

    #1633943

    ramyours2003 (7/18/2013)

    .TUF -transaction undo file

    If you have your logshipped database in standby mode and you delete the .TUF file you'll need to re establish the log shipping plan.

    In short don't delete the file and don't let other users delete it either!

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • July 19, 2013 at 5:39 am

    #1633946

    HanShi (7/18/2013)

    SQL Server doesn't have a Transaction Undo File. I think you are working with Oracle. This forum is about Micorosoft SQL Server. Very few posters will have extensive experience with Oracle.

    Log shipped databases in standby mode have a .TUF file which is used for recovering the database for read only purposes (or Standby mode).

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • July 19, 2013 at 5:53 am

    #1633957

    Thanks Perry... I was unaware about this TUF file fact...

    _______________________________________________________________
    To get quick answer follow this link:
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

  • July 19, 2013 at 5:57 am

    #1633959

    kapil_kk (7/19/2013)

    Thanks Perry... I was unaware about this TUF file fact...

    Books Online is very clear on this, it must not be manually deleted other wise the database will need to restored. Best to use NTFS ACls to protect the folder that the file resides in and grant delete on this file only to the SQL Server service account.

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • July 19, 2013 at 6:58 am

    #1633993

    Perry Whittle (7/19/2013)

    kapil_kk (7/19/2013)

    Thanks Perry... I was unaware about this TUF file fact...

    Books Online is very clear on this, it must not be manually deleted other wise the database will need to restored. Best to use NTFS ACls to protect the folder that the file resides in and grant delete on this file only to the SQL Server service account.

    There is one exception though. If, for whatever reason, you need to rebuild your LS configuration, the 'old' tuf-file can be removed.

  • July 19, 2013 at 7:22 am

    #1634012

    LS can be configured in two ways (i) No-recovery mode (No one can access the database)

    (ii) Standby/ Readonly mode (Users will be able to access the database - main purpose is for reporting). When you configure in Readonly mode, it requires to provide tuf (transaction undo file) location. It will collect all the uncommitted transactions in the log file.

    When the logshipping is alive, no one can delete the tuf file - it wont allow and say 'file in use'. You will be able to delete or copy it only when LS is stopped/ broken.

    If it is deleted by chance, LS won't work - either has to be replaced with the right tuf file or reconfigured from scratch.

Viewing 10 posts - 1 through 9 (of 9 total)

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