Holger Degroot (6/2/2009)
Hi Paul,yes it was the first and only error.
If that's the case, I would suggest two things before you try a fix.
1) Evaluate your IO subsystem - check for errors in event logs or RAID error logs
2) Get that database onto different disks or a different IO system completely.
If you've got new corruptions appearing then there's a serious problem here.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability