I suppose the important thing is to define what encompasses "Database
is Corrupt"? Database is inaccessible; e.g. any attempt gives an error
saying "Database is Corrupt"? Database is accessible but access to the
data fails; i.e. no TABLE in the Database can be accessed? Data
corruption? Index corruption as in wrong row? Index corruption as in
rebuild-required? Catalog functional errors? Catalog data errors? A
particular SQL request does not function properly? Some particular
thing about the database does function properly?
Only by knowing what that definition is, can any legitimate contrasts
and comparisons be made to the DB2 for i [(or DB2/400) for which "the
Database" is the *SYSBAS ASP and the OS, or the iASP and the OS].
Regards, Chuck
On 29 Jan 2013 13:02, Roger Harman wrote:
<<SNIP>> A recent article, "My SQL Server Database is Corrupt - Now
What?!" <<SNIP>>
I'm curious.. How many of you have seen corruption on our platform?
In 25+ 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.
<<SNIP>>
