Check New Horizons, They used to offer that kind of class.

Also you might want to try search "cbt clustering class sql server" on the web

This option does not prevent torn pages, it only tells you if you have one. Once it discovers one, your database is marked

as corrupt, and all you can do...

Turn torn page detection off, if enabled.

You might want to run DBCC UpdateUsage (Your DB ) after that.

You can run a Profiler first(if system permits)

SELECT sysobjects.name as 'Table Name', syscolumns.NAME AS 'Identiy Column Name'

FROM syscolumns, sysobjects

WHERE syscolumns.ID = sysobjects.ID

and sysobjects.name in (select name...

As hoo-t mentioned earlier by utililizing SQL LiteSpeed you could do a backup ( backup using SQL LiteSpeed could be around 8-10GB) and then you could do a restore over...

Or:

EXECUTE sp_MSforeachtable

        @command1=" Print '?' EXECUTE sp_spaceused '?'"

823 is a hardware error. Did you check Event viewer for any disk errors; controller? You might also run CHKDSK and see output.

Can't just put a backup script in a 1st step in a Job and notification ( success/fail) as 2nd/3rd step?

You might want to explore the below script (more on a create rather on an update):

Select name, xtype, crdate from dbo.sysobjects where crdate > getdate()-3 and name not like '%temp%'...

Attach will be a time saver vs backup/restore when comes to the big DB's (hundreds of GB)

t/a stands for transaction(s).

To reduce the allocation resource contention for tempdb that is experiencing heavy usage you might want to increase the number of tempdb data files with equal sizing.

can you try something like that:

Create another job (will run every day) and put the following:

if the date of the insert in the table is old THEN 14 DAY

BEGIN

msdb..sp_start_job '

post your resume on dice or monster.