TheSQLGuru (5/7/2014)

---

Also note that you stated that 9,999 times out of 10,000 that the IO subsystem was responsible for corruptions. Same type of probabilistic statement - just with a...

Grant Fritchey (5/7/2014)

---

jcrawf02 (5/7/2014)

---

ChrisM@Work (5/7/2014)

---

DBCC TIMEWARP?

I was tempted to suggest that only IBG and Jeff's queries can run that fast. Also, that queries running that fast can overheat the processor...

SQL doesn't use high-precision timers (too resource intensive). Inaccuracy in the order of a few ms is not a problem. Like most rounding issues, the large numbers are accurate enough...

humbleDBA (5/7/2014)

---

but there are enough myths and misconceptions in the SQL Server community...with 'incremental' being one I've heard before (in relation to backups) and they are not, they are different-ial....

I'm not willing to guess...

You need to figure out why Windows can't see them. Chat with the VM admin. Once Windows can see the processors, then SQL should be able to with at most...

humbleDBA (5/7/2014)

---

Ok, I'd hate to think I've missed something with regard to SQL Server, but my understanding is that there is no such thing as 'Incremental' backups, as in each...

Can Windows see the CPUs?

Were they hot-added?

What edition of SQL?

Schedulers != CPUs.

You have 8 CPU cores, that means 8 visible online schedulers (one for each core). The hidden schedulers are for background tasks or the DAC, they're created in...

Corruption is 99.99% IO subsystem problem. Not necessarily the disks, could be anything anywhere in the IO stack.

Since you mentioned an uncontrolled shutdown, I'd check and make sure all write...

Anything like an index rebuild occur between the backup and the checkDB?

Yes, you can use sys.partitions if you want unfiltered row count. If you want to query the table directly, then SELECT COUNT(*) ...

Well, not skews results so much as causes task manager to mis-report.

Performance Monitor. Easiest is total server memory under (I think) the SQL Server Memory Manager. You can also go...

Never use task manager to check SQL's memory. It reports incorrect values when SQL is using locked pages.

The page size is not a concern, 8GB is probably what you have...

What do you mean by '200MB of data' and where are you seeing that?