restore transaction log.

Dear friends,
I do transaction log backup 3 times a day 11:30 am, 05:00
pm, 07:00 pm. My question is
1. If I restore transaction log, Do I need restore all
transaction log or only the latest transaction log.
thx."kresna rudy kurniawan" <kresnark@.yahoo.com> wrote in message
news:00ef01c378e2$2f125b20$a001280a@.phx.gbl...
> I do transaction log backup 3 times a day 11:30 am, 05:00
> pm, 07:00 pm. My question is
> 1. If I restore transaction log, Do I need restore all
> transaction log or only the latest transaction log.
> 1. If I restore transaction log, Do I need restore all
> transaction log or only the latest transaction log.
Since the transaction log records each change in sequence, you'll need to
restore all the transaction log backups (in sequence).|||"David Campbell" <dave_gc_nospam@.hotmail.com> wrote in message
news:vm2j3l3e5sa44b@.corp.supernews.com...
> "kresna rudy kurniawan" <kresnark@.yahoo.com> wrote in message
> news:00ef01c378e2$2f125b20$a001280a@.phx.gbl...
> >
> > I do transaction log backup 3 times a day 11:30 am, 05:00
> > pm, 07:00 pm. My question is
> >
> > 1. If I restore transaction log, Do I need restore all
> > transaction log or only the latest transaction log.
> > 1. If I restore transaction log, Do I need restore all
> > transaction log or only the latest transaction log.
> Since the transaction log records each change in sequence, you'll need to
> restore all the transaction log backups (in sequence).
Mr Cambell is absolutely correct. However, if when you backup each log you
specify the option 'with no_truncate' then you would only need to restore
the last log backup. The drawback of this is that your log file will grow
and grow, so you might want to consider immediately before your full backup
backing up the log with the default of 'with truncate'|||> However, if when you backup each log you
> specify the option 'with no_truncate' then you would only need to restore
> the last log backup.
Note that BOL, for the NO_TRUNCATE, parameter say:
"Allows backing up the log in situations where the database is damaged."
Based on that, I would say that using the NO_TRUNCATE option for other purposes isn't supported (as
it isn't documented). Personally, I'd prefer if MS either renamed this option, or documented
explicitly whether it is supported to use for such backup scenario.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"bob simms" <bob_simms@.hotmail.com> wrote in message news:OuvE15QeDHA.1736@.TK2MSFTNGP12.phx.gbl...
> "David Campbell" <dave_gc_nospam@.hotmail.com> wrote in message
> news:vm2j3l3e5sa44b@.corp.supernews.com...
> > "kresna rudy kurniawan" <kresnark@.yahoo.com> wrote in message
> > news:00ef01c378e2$2f125b20$a001280a@.phx.gbl...
> > >
> > > I do transaction log backup 3 times a day 11:30 am, 05:00
> > > pm, 07:00 pm. My question is
> > >
> > > 1. If I restore transaction log, Do I need restore all
> > > transaction log or only the latest transaction log.
> > > 1. If I restore transaction log, Do I need restore all
> > > transaction log or only the latest transaction log.
> >
> > Since the transaction log records each change in sequence, you'll need to
> > restore all the transaction log backups (in sequence).
> Mr Cambell is absolutely correct. However, if when you backup each log you
> specify the option 'with no_truncate' then you would only need to restore
> the last log backup. The drawback of this is that your log file will grow
> and grow, so you might want to consider immediately before your full backup
> backing up the log with the default of 'with truncate'
>

Restore MSDB without reinstalling SQL server

Hello Friends,

I my sql server, the microsoft db msdb is displaying as Suspect. As a result of this, many of the transaction that involves SQL server fails. Is there any solution to correct this db without reinstalling SQL Server. Will it work if I copy the msdb of another SQL Server to my server and attach that database to mine.

Thanks and regards,

Babz

Hi,

you sure have a backup of MSDB, then you can use the following article:

http://msdn2.microsoft.com/en-us/library/ms190749.aspx

If not, you can try to attach the files shipped with the original install media. This might work in your case, but changes in your original msdb database (jobs etc) will be lost.

Jens K. Suessmeyer

http://www.sqlserver2005.de