No data file,damaged SQL Server,any chance to backup transaction l

Hi,
No data file,damaged SQL Server,any chance to backup transaction log? (MS
SQL Server 2000 SP3)
-- Many thanks, Oskar.
Hi,
no data file, no backup, no database. You cannot restore the database
from the transaction logfiles.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Hi Oskar
"Oskar" wrote:

> Hi,
> No data file,damaged SQL Server,any chance to backup transaction log? (MS
> SQL Server 2000 SP3)
>
You will have to go back to the last good full backup. Do you have scheduled
backups or backups on tape?
John
|||Thanks John. I'm not actually experiencing this problem at the moment. I was
just wondering if in theory it is possible to make the last transaction log
backup of a database if its data file and the server to which it was attached
are gone. And I came to a conclusion that it probably is - one could try to
restore the master database on a (virtual) test server and copy the salvaged
transaction log file onto the same drive letter it was on the original
server, and then make the last backup of the transaction log so that no
transactions are lost during recovery.
-- Oskar
"John Bell" wrote:

> Hi Oskar
> "Oskar" wrote:
> You will have to go back to the last good full backup. Do you have scheduled
> backups or backups on tape?
> John
>
|||Hi Oskar
"Oskar" wrote:

> Thanks John. I'm not actually experiencing this problem at the moment. I was
> just wondering if in theory it is possible to make the last transaction log
> backup of a database if its data file and the server to which it was attached
> are gone. And I came to a conclusion that it probably is - one could try to
> restore the master database on a (virtual) test server and copy the salvaged
> transaction log file onto the same drive letter it was on the original
> server, and then make the last backup of the transaction log so that no
> transactions are lost during recovery.
> -- Oskar
>
To backup the transaction log you will need the database to be working, in
which case not having the mdf file (as per your original post) will not allow
this. There is no substitute for having a proper backup regime and storing
the backups safely.
John
|||John, but how about the NO_TRUNCATE clause of the BACKUP LOG command. BOL
says it allows the final log backup to be made even when data files are lost
so that one can recover up to the point of failure (of data files). The case
I described differs only in that the server itself is also gone.
-- Oskar
"John Bell" wrote:

> Hi Oskar
> "Oskar" wrote:
> To backup the transaction log you will need the database to be working, in
> which case not having the mdf file (as per your original post) will not allow
> this. There is no substitute for having a proper backup regime and storing
> the backups safely.
> John
|||Hi Oskar
The log can still be backed up when the database is suspect see
http://www.karaszi.com/sqlserver/info_corrupt_suspect_db.asp I guess you
would need to try it.
John
"Oskar" wrote:
[vbcol=seagreen]
> John, but how about the NO_TRUNCATE clause of the BACKUP LOG command. BOL
> says it allows the final log backup to be made even when data files are lost
> so that one can recover up to the point of failure (of data files). The case
> I described differs only in that the server itself is also gone.
> -- Oskar
> "John Bell" wrote: