MSDE corruptions, the new TAM corruption

Update packages to a new full were failing.  We were getting the following message on the deployment server (which has been working like clock-work)  I said clock!

The logs say things like:

3328/744 FOREIGN_THREAD                             Tue Mar 24 20:24:21.669000                   Jdekprnt.c1086

            KNT0000119 - PRTTable_GetDefaultPrinterInfo failed to find printer:   User: JDEDBA Host: WinClient

3328/744 WRK:Starting jdeCallObject                  Tue Mar 24 20:24:22.638000                   pkgInit.cpp739

            PKGINT0023 - Package: PY812CU02. PathCode: PY812. Update parent package. Wait for BUSBUILD. Data by PathCode. Update Package.

But the kicker was:

3328/744 WRK:Starting jdeCallObject                  Tue Mar 24 20:25:15.233001                   Jdbodbc.c8330

            ODB0000164 - STMT:00 [HY000][823] [Microsoft][ODBC SQL Server Driver][SQL Server]I/O error (bad page ID) detected during read at offset 0x00000052e72000 in file 'D:\JDEdwards\E812\PY812\package\PY812CF\pkgspec\SPEC__PY812CF.mdf'.

So, I tried a query through Enterprise Manager and was greeted with the same errors:

Server: Msg 823, Level 24, State 2, Line 1

I/O error (bad page ID) detected during read at offset 0x00000052f74000 in file 'D:\JDEdwards\E812\PY812\package\PY812CF\pkgspec\SPEC__PY812CF.mdf'.

Connection Broken

Therefore, it seems that MSDE corruptions might be the new TAM corruption of old!  Woopie.