Log shipping and database corruption

Hi,
Could anyone please explain to me how the corruption of a primary database
can be carried to the secondary database by means of the log shipping? Can
these corruptions be spotted at the secondary server? Will any error messages
be generated? Both the primary and the secondary are MS SQL Server 2000 SP3.
-- Many thanks, OskarLog shipping will carry whatever that can be backed and restored. This may
include certain physical corruptions and all logical corruptions (i.e. with
respect to the app logic).
I don't have the exact breakdown of what corruptions do or do not lead to a
backup/restore failure or error. But it may help to DBCC the restored copy.
But in practice, I have to admit that I have not seen, for at least several
years now, a case where a corruption is caught by DBCC'ing the restored
database but not already shown up in the primary.
Linchi
"Oskar" wrote:
> Hi,
> Could anyone please explain to me how the corruption of a primary database
> can be carried to the secondary database by means of the log shipping? Can
> these corruptions be spotted at the secondary server? Will any error messages
> be generated? Both the primary and the secondary are MS SQL Server 2000 SP3.
> -- Many thanks, Oskar|||Do you also know whether every corruption that leads to data loss is logged
into the primary errorlog as soon as it happens? That would be just sensible,
wouldn't it?
-- Oskar
"Linchi Shea" wrote:
> Log shipping will carry whatever that can be backed and restored. This may
> include certain physical corruptions and all logical corruptions (i.e. with
> respect to the app logic).
> I don't have the exact breakdown of what corruptions do or do not lead to a
> backup/restore failure or error. But it may help to DBCC the restored copy.
> But in practice, I have to admit that I have not seen, for at least several
> years now, a case where a corruption is caught by DBCC'ing the restored
> database but not already shown up in the primary.
> Linchi
> "Oskar" wrote:
> > Hi,
> > Could anyone please explain to me how the corruption of a primary database
> > can be carried to the secondary database by means of the log shipping? Can
> > these corruptions be spotted at the secondary server? Will any error messages
> > be generated? Both the primary and the secondary are MS SQL Server 2000 SP3.
> >
> > -- Many thanks, Oskar|||No, it isn't. It is logged when it is detected which is normally when the
data needs to be read back off of disk for some reason.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Oskar" <Oskar@.discussions.microsoft.com> wrote in message
news:37E006FF-F6B0-41E9-9FE9-C54F905940F1@.microsoft.com...
> Do you also know whether every corruption that leads to data loss is
> logged
> into the primary errorlog as soon as it happens? That would be just
> sensible,
> wouldn't it?
> -- Oskar
> "Linchi Shea" wrote:
>> Log shipping will carry whatever that can be backed and restored. This
>> may
>> include certain physical corruptions and all logical corruptions (i.e.
>> with
>> respect to the app logic).
>> I don't have the exact breakdown of what corruptions do or do not lead to
>> a
>> backup/restore failure or error. But it may help to DBCC the restored
>> copy.
>> But in practice, I have to admit that I have not seen, for at least
>> several
>> years now, a case where a corruption is caught by DBCC'ing the restored
>> database but not already shown up in the primary.
>> Linchi
>> "Oskar" wrote:
>> > Hi,
>> > Could anyone please explain to me how the corruption of a primary
>> > database
>> > can be carried to the secondary database by means of the log shipping?
>> > Can
>> > these corruptions be spotted at the secondary server? Will any error
>> > messages
>> > be generated? Both the primary and the secondary are MS SQL Server 2000
>> > SP3.
>> >
>> > -- Many thanks, Oskar