I think you've got it backward...
I don't believe it even possible for a SAVE to damage an object. But a
damaged object is often detected during the SAVE operation.
On Tue, Jan 29, 2013 at 4:45 PM, Jim Oberholtzer<
> The question of if a damaged object is considered a corrupted file then
> yes, I have seen it. Usually it's as the result of a Save/Restore
> operation that failed, but it does happen.
> Jim Oberholtzer
> Chief Technical Architect
> Agile Technology Architects
> On 1/29/2013 3:02 PM, Roger Harman wrote:
> > A recent article, "My SQL Server Database is Corrupt - Now What?!", had> some
> > interesting statements from the author:> world.
> > . I was asked how often corruption really occurs in the real
> > My answer was, "hundreds to thousands of times every week across the> world,
> > in the tens of millions of SQL Server databases.".> advice
> > . Every single week I receive multiple emails asking for some
> > about corruption recovery. When I'm teaching about corruption in our High> class
> > Availability and Disaster Recovery Immersion Event, I always tell the
> > that I expect every DBA to see database corruption at some point during> happen
> > their career.
> > . I'll end by saying this: if you think that corruption won't
> > to you at some point in your career, I think you'll be surprised. Be> 25+
> > prepared!
> > I'm curious.. How many of you have seen corruption on our platform? In
> > years on S/38, AS/400, and IBM-i, I have NEVER had an issue with corrupt
> > files/tables. In 1 year of SQL Server at my former employer, I saw it
> > happen at least 3 times. I was shocked but the Microsoft bigots in the
> > company just shook it off as status quo.
> > Here's the article but you have to be a member to read it.
> > http://www.sqlservercentral.com/articles/Corruption/96117/
> > --
amazon.com ads help fund midrange.com operations