That's a table that's corrupt.

In this case, I suspect that a repair with allow_data_loss will work and will not lose data (there are no row that are unreadable,...

The first 8 pages this morning had 3 legit posts on them, in total

Unless you have a really good reason to be fiddling with that config setting, rather leave it alone.

No where near enough information. To come up with a DR plan, you need to identify the SLAs and requirements. How much data loss is tolerable? How much downtime is...

I'd use transactional replication and schedule the distribution agent to run every 4 hours. That way you snapshot once (when you set it up), not every 4 hours.

https://connect.microsoft.com/SQLServer/feedback/details/377223/sys-master-files-does-not-show-accurate-size-information

No, the transaction name is not causing the duplicates.

If SQL says you have duplicate rows, then you have duplicate rows. Probably due to using the read-then-insert pattern without...

Sys.master files is the size at last start of SQL Server iirc, so you probably have a very low default size for TemoDB and it has to grow afterwards (which...