SQLBill (6/25/2015)

Okay, so how many looked at the cat and then looked at the books and thought "I have that one, don't have...

I took all of my Game of Thrones books down to...

What's the issue?

You've described a scenario, but haven't said what exactly is wrong.

Also, have you either scheduled log backups or put the DB into simple recovery (depending on recovery...

When I was still blogging, it was very rare that something I wrote was related in any way to what I was working on. More often they were inspired by...

I'm going to disagree with you there.

Large transaction log will not result in lots of log backups.

Lots of VLFs won't result in lots of log backups.

You get log backups when...

I found a photo of my Siamese.

*sniff*

No.

Availability groups requires full recovery model. In full recovery model, the transaction log is only marked reusable when a log backup runs.

Couple things jump out.

Nolock hints, do you know what they do? (hint, they don't make queries faster)

Scalar UDFs are notorious performance problems. Consider converting this to an in-line table function...

Probably Querying.

The Window functions book is excellent, but has a very narrow scope and is reasonably advanced.

Please run the following and post the full and unedited output. Not all corruptions are repairable.

DBCC CheckDB ('<Database name>') WITH NO_INFOMSGS, ALL_ERRORMSGS

Also can you run:

SELECT name, df.state_desc, df.is_read_only FROM sys.database_files...

Because the first time you run a query the data has to be loaded from disk. Disk is slow. After that first execution, SQL Server can read the pages from...

Disks are slow, memory is fast. Therefore when SQL reads a page off disk it puts it into the data cache so that if it needs to read it again,...

Loading data from disk into the data cache

Compiling the query the first time and placing the plan into the plan cache

The first is usually a far larger impact than the...

A parallelism operation.

That's also why there are so many empty...

It just means that someone was trying to connect while SQL was still starting up. It's not an error.