Re: Applying tranaction log to old data file

> DO NOT DO TRUNCATE ONLY - YOU WILL LOOSE YOUR LOGS FOR GOOD!!!!!!!

Yes, I meant NO_TRUNCATE as in the original example I posted.  I don't 
believe the TRUNCATE_ONLY option is allowed when the data files are 
inaccessible.

Thanks for the correction.

-- 
Hope this helps.

Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/

"Sybaseguru" <collap@[EMAIL PROTECTED]
> wrote in message 
news:4863d830$0$25950$6e1ede2f@[EMAIL PROTECTED]
>>
>> You should be able to backup the transaction log using the
TRUNCATE_ONLY
>> option even if the data file(s) is unavailable.
>>
> DO NOT DO TRUNCATE ONLY - YOU WILL LOOSE YOUR LOGS FOR GOOD!!!!!!!
>
> The procedure you need is in 3 parts:-
>
> Firstly you need to dump the 24gb transaction log - ie take it out of
the
> database onto a file system file. Read up on "dump tran...no_truncate".
> This will work even if the data is stuffed as long as the log is intact.
>
> Secondly you use you old dump from yonks ago to reset up the database.
If
> the disks are ok you can just use "load database"
>
> Thirdly you apply the transaction log that you saved in the first step. 
> read
> up on "load tran"
>
> The secret is in the planning of the recovery. If you've got space you
can
> create a whole new databse and do the recovery to that and when you are
> happy rename the databases and cycle the server.
>