Well,

I restored the database on a different server and same MS-SOL flavor (or almost) but it's the best I can do, I have no more available servers and space for that.

It took a while, but it's there and NOT in a suspect state; database is open and available. That's good!

Now I am running (on that standby server) a DBCC CHECKDB and waiting for results. Crossing fingers! :unsure:

I still believe is not data corruption, but if DBCC command via console gave errors (hopefully it will not) here's what I am planning to do;

Run this

DBCC TRACEON (3604, -1)

GO

DBCC PAGE('MyDatabase', 1, 12345, 3)

GO

Where 12345, would be the corrupted data page? Hopefully it won't be a Clustered Index. If it's a non clustered Index, drop it and recreate it. Otherwise, go back a few weeks and check backups.

I do not know if I should re-run the DBCC command via Maintenance Plan if the DBCC command via console gives errors. That may be the issue, and not real data corruption.