restore tran log

hi;
under what situation will we call for these different actions:
1) restore tran-log (made since previous full bck) in sequence after lastest
back up is restored
2) restore only the latest tran-log (made since previous full bck) after
latest full bck up is restoredI do not think it's possible to just apply the latest transaction log, if
there had been other transaction log backups made since the last full
backup, unless the NO_TRUNCATE option was used. If this was the case, it
would be equivalent to performing a differential backup.
Regards
Ray
"pk" <pk@.> wrote in message news:OSa7NWWEEHA.3748@.TK2MSFTNGP11.phx.gbl...
> hi;
> under what situation will we call for these different actions:
> 1) restore tran-log (made since previous full bck) in sequence after
lastest
> back up is restored
> 2) restore only the latest tran-log (made since previous full bck) after
> latest full bck up is restored
>|||Ray is correct, you can not skip past restoring one tran log and then
restore a more recent log...SQL checks and requires that logs be restored in
the proper order..
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"pk" <pk@.> wrote in message news:OSa7NWWEEHA.3748@.TK2MSFTNGP11.phx.gbl...
> hi;
> under what situation will we call for these different actions:
> 1) restore tran-log (made since previous full bck) in sequence after
lastest
> back up is restored
> 2) restore only the latest tran-log (made since previous full bck) after
> latest full bck up is restored
>

Restore to a previous version

Is it possible at all to restore back up from SQL 2005 onto SQL 2000?

If not, what is the bast way to transfer database stucture and data from SQL 2005 onto SQL 2000. Two machines are not on the same network...

No, it is not possible to restore a SQL 2005 server on SQL 2000.

You can script the database to a file and then apply to SQL 2000. Since your servers are not on the same network, the best option would be to export/import using bcp or BULK INSERT. Books on-line would have more information.

Peter

Restore Previous Backup on Logshipping Primary

Quick Question: If I want to restore an earlier database backup (rollback)
my log shipping primary - how do I ensure that I get my secondaries in sync?
Just re-create the maintenance plan? The database in question is very large,
and I'd like to be able to just do a point-in-time restore on the primary,
etc, without messing up my transaction log lineage.
Does anyone have any scripts handy?
TIA
J Roberts
Norfolk ITJohn
Backup Log file before restore full database
Disable Log Shipping
Restore the database and apply all log file/s with option at point of
time. Then enable Log Shipping and restore full and then log file backpus on
the secondary server
Actually I have not used maintenance paln fo doing Log Shipping , as I
always create scripts (stored proceduers etc..)
"John Roberts" <JohnRoberts@.discussions.microsoft.com> wrote in message
news:094ACA2D-1C92-47DE-B63C-7E7A4087FE7B@.microsoft.com...
> Quick Question: If I want to restore an earlier database backup
> (rollback)
> my log shipping primary - how do I ensure that I get my secondaries in
> sync?
> Just re-create the maintenance plan? The database in question is very
> large,
> and I'd like to be able to just do a point-in-time restore on the primary,
> etc, without messing up my transaction log lineage.
> Does anyone have any scripts handy?
> TIA
> J Roberts
> Norfolk IT|||That's what I thought. You'd think that MS would have considered rollbacks
in their implementation... Oh well. T-SQL it is. I think I'm going to use
SQL-DMO (vb.net) for this...
Thanks for your reply.
John
"Uri Dimant" wrote:
> John
> Backup Log file before restore full database
> Disable Log Shipping
> Restore the database and apply all log file/s with option at point of
> time. Then enable Log Shipping and restore full and then log file backpus on
> the secondary server
> Actually I have not used maintenance paln fo doing Log Shipping , as I
> always create scripts (stored proceduers etc..)
>
>
> "John Roberts" <JohnRoberts@.discussions.microsoft.com> wrote in message
> news:094ACA2D-1C92-47DE-B63C-7E7A4087FE7B@.microsoft.com...
> > Quick Question: If I want to restore an earlier database backup
> > (rollback)
> > my log shipping primary - how do I ensure that I get my secondaries in
> > sync?
> > Just re-create the maintenance plan? The database in question is very
> > large,
> > and I'd like to be able to just do a point-in-time restore on the primary,
> > etc, without messing up my transaction log lineage.
> >
> > Does anyone have any scripts handy?
> >
> > TIA
> >
> > J Roberts
> > Norfolk IT
>
>