33 slides for 3 hours. Should be enough.

Use 1222. 1204 is legacy, for SQL 2000 and before. Less info, harder to read, much harder to debug.

Also watch out for large file copies and make sure you're running updated drivers for RAID/storage.

I didn't say they're the best thing out there. Just that they're not useless (which many say they are)

Both of those covered in the 'considerations for nonclustered indexes' section.

One more added - Indexes with a leading bit column are useless

Edit: and another - Optimiser's choice of seek/scan is...

In that case you need to figure out what is requesting memory from Windows such that it's paging SQL out. It'll only do that if it is under memory pressure...

Definitely will address that one, along with the related 'nonclustered index sorts physically', since they are pet peeves...

That's a little high. On a 32 GB server, I'd probably be looking...

Sequence objects are new in SQL Server 2012, if that's what you mean.

kapil_kk (8/26/2013)

---

is it...

So the current list is:

No need to index small tables

No need to index tables that fit into memory

Indexes enforce physical order of data

Seeks are better than scans

Clustered index seek/scan is...

Procedure cache is the old name for the plan cache.

Plan cache - cache of compiled query plans so that the optimiser doesn't have to regenerate them

Data cache - cache of...

Grant Fritchey (8/26/2013)

---

Don't forget the "one true index." All we need is a single, perfect, clustered index that will be all things to all people for all queries for all...

It's called triggers and audits, along with properly configured security (minimal permissions)

CheckDB creates a hidden snapshot to run against, to allow it to have a transactionally consistent view of the database. That's just the LSN that the database was at when...