I'm with...

Bear in mind that it's not going to match the size of the log backups exactly and if you're compressing the log backups it's not going to match at all.

'Never' is a good frequency for shrinking logs.

If your DB is in full recovery and you're not doing log backups, either put the DB into simple recovery model or start taking log backups. If you don't do...

There's nothing stupid about it.

In simple recovery model you're telling SQL...

It's critical in TempDB to spread out the allocation of tables across the files and hence reduce the contention on the first set of allocation pages in the file. If...

Grade IN ('A','B','c','D','E','F','G')

etc

No, you can't use fn_dblog as in simple recovery model the log is truncated on every checkpoint, so every couple minutes.

Best thing, prior to implementing log shipping, switch the DBs...

Ok, that's pretty big.

http://www.sqlskills.com/blogs/paul/checkdb-from-every-angle-consistency-checking-options-for-a-vldb/

If it wasn't January, I'd be wondering if this was a mis-scheduled April Fools joke. Seriously, whoever crafted those 'recommendations' should probably not be allowed anywhere near a database server,

Page IO latch is indicative of IO activity, as Grant mentioned but PageLatch isn't. Depending on what kind and what resource it could, if high enough, be indicating allocation contention...

http://www.urbandictionary.com/define.php?term=polite

JarJar (1/14/2015)

---

it's my understanding that data is striped across the files of a filegroup using a proportional fill algorithm, so if one file is larger than the others it gets...

It's TempDB where the files MUST be the same size. For user databases isn't not particuarly critical.

It is a bit odd to see 8 files in the primary filegroup though....

What?

Your example above created a column with identity, so why are you asking how to create a column with identity?