September 22, 2011 at 5:41 am
Processed 16 pages for database 'Fgb', file 'FG_1' on file 1.
The roll forward start point is now at log sequence number (LSN) 35000000119200001. Additional roll forward past LSN 35000000130100001 is required to complete the restore sequence.
RESTORE DATABASE ... FILE=<name> successfully processed 16 pages in 0.085 seconds (1.470 MB/sec).
Thanks
September 22, 2011 at 5:47 am
You either forgot a log backup or the table was gone by the time you took the full or diff.
What's left is if the table is in the full but not after the logs, then you can use the STOPAT option. You need to figure out the correct time. If you go too far then you need to restart from the begining.
You can use the with standby option to have readonly access on the db to see if you have your data back before doing more tlog restores (or later PIT restore in the same tlog).
September 22, 2011 at 5:52 am
forsqlserver (9/22/2011)
The roll forward start point is now at log sequence number (LSN) 35000000119200001. Additional roll forward past LSN 35000000130100001 is required to complete the restore sequence.
That message means you need to restore one-or-more log backups before you can bring the file online.
I get the impression you're trying to restore a file to an earlier time? If so, that's not possible. When restoring part of the database (file, filegroup or page) you have to restore log backups to bring it up to the same time as the rest of the database. You can't restore a file from a backup and leave it at an earlier point in time.
If you're trying to recover a dropped table from a backup, you need to restore to a new database, roll forward as far as you need then copy the data over.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply