Backing up a damaged database

Question

Backing up a damaged database

Steve Jones - SSC Editor

SSC Guru

Points: 736183
More actions
February 8, 2023 at 12:00 am

#4138718

Comments posted to this topic are about the item Backing up a damaged database

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Jeff Moden SSC Guru Points: 1004329 More actions · Answer 1

I'm going to venture out and say that what you have as the correct answer isn't the correct answer. It doesn't even appear on the page you referenced.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

far SSCertifiable Points: 6575 More actions · Answer 2

far

SSCertifiable

Points: 6575

February 8, 2023 at 7:11 am

#4146909

The correct Answer choice was not available

Steve Jones - SSC Editor SSC Guru Points: 736183 More actions · Answer 3

typing while not thinking. This is fixed. The no_truncate option is needed

Jeff Moden SSC Guru Points: 1004329 More actions · Answer 4

Steve Jones - SSC Editor wrote:

typing while not thinking. This is fixed. The no_truncate option is needed

None of us has ever done that before, right? 😀 😀 😀 Thanks, Steve.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Mark D Powell SSCarpal Tunnel Points: 4775 More actions · Answer 5

From the reference page, if a database is damaged, try to take a tail-log backup by using the WITH CONTINUE_AFTER_ERROR option of the BACKUP statement. Also on that page, Important: Avoid using NO_TRUNCATE, except when the database is damaged. Seems to me best answer included both these options.

Forgot to include MS reference: Tail-Log Backups (SQL Server) - SQL Server | Microsoft Learn

https://learn.microsoft.com/en-us/sql/relational-databases/backup-restore/tail-log-backups-sql-server?view=sql-server-ver16

This reply was modified 1 year, 9 months ago by Mark D Powell.
This reply was modified 1 year, 9 months ago by Mark D Powell.