do SS transaction logs have to be backed up for recovery to POF?

Coming from a (mostly) Oracle shop, I am unclear how SS transaction logs work as far as up to point of failure recovery goes.

I have the few MSSQL databases I look after in full recovery mode, and I set up maintenance plans to back these up online on a daily basis. In the research I did it was recommended backing up the transaction logs as well on a frequent basis to ensure recovery to POF or point in time.

I had assumed that they work like Oracles archive logs, in that once they are full they are archived to disk in case they are needed, to duplex destinations if need be. Does SS do this, or do I need to be backing up transaction logs on an hourly (or shorter) basis? In looking at enterprise manager I see that it does not look like the transaction logs are archived anywhere, but overwritten once filled up, similar to Oracle noarchivelog mode, in that if you lose your online redo logs or anyone of them has recycled since your last backup, then you can only recover to the last good backup.

Is this a correct assumption? Should I be backing up transaction logs hourly to make sure I can have PIT or POF recovery?

thanks

TG
.

Relevant Pages

  • Re: MSDB database
    ... sort of contradicts the line from BOL "All recovery ... i don't back up transaction logs. ... i think it's sort of goofy that the transaction log backup from a dbmp will try ...
    (microsoft.public.sqlserver.server)
  • Re: Sharepoint transaction logs
    ... Perhaps you should just backup your transaction logs, ... > the portal_Site transaction log files do not shrink. ... > Has anybody just kept the portal_Site db recovery option to simple? ...
    (microsoft.public.sharepoint.portalserver)
  • Re: Backup - truncating log?
    ... If you don't want the transaction logs, use ALTER DATABASE dbname SET ... If you actually need to truncate the log, ... However you should read about recovery plans in the BOL in order to make ...
    (microsoft.public.sqlserver.server)
  • Re: Crossing over from SQL Server
    ... mix of SQL Server and Oracle. ... Just to add to what the others have told you(I look after both MSSQL and Oracle db's), get yourself used to the following: ... You don't have to back up your transaction logs as part of your backup strategy to have point in time recovery capability, Oracle logs its transaction logs to disk automatically when you are in archivelog mode, and you can have them written to disk to multiple locations. ...
    (comp.databases.oracle.server)