Thanks all for the good feedback!

Steve, just to clarify, I didn't mean to imply we had Dev and Prod code on the same server. We of course have a separate...

Thanks Tim.

We don't have quite the distinction between Dev and Prod unfortunately.

Along your thoughts of optimizing for load, I'm leaning toward limiting cross server queries. We do a lot...

Welsh, thanks for the response.

My question was really looking for general theory on why you would choose to group databases together. That said, I do a fair amount of...

Thanks for the response Colin.

Recognizing there is no correct answer, all thoughts and ideas are helpful!

Look up "default trace" in BOL.

This server option is turned on by default. There's little documentation on when and what data it collects, however, you may be able to...

Hmmm...I would have thought TRUNCATE could raise a DDL trigger.

Generally that is all there should be. However, there are certain nuances with the LocalSystem account that I'm not familiar enough to speak to.

When using Windows Authentication - that user must have file system permissions to the file. When using SQL Server authentication - the service account that runs the SQL Server services...

Thanks for the suggestion Paul.

So I had to wait until after Thanksgiving for my maintenance window. I downloaded the Hotfix and went to install it and got this message:

This SQL...

Thanks for the response guys..

Unixbomer: Yes, "SELECT * FROM ::fn_dblog(NULL, NULL)" does show a checkpoint occurred, however it was over 12 hours ago.

Steve: It's tough to tell the size of...

The last couple hours I've been watching the log go from 95, to 96...it's now over 99% full. I expect auto grow to occur at any moment. If that occurs,...

Fair question...I had to double check myself, but yes, it's in SIMPLE.

Yes, manually executing CHECKPOINT flushes the log.

This is an old database and the log was set to auto grow by small increments so I thought maybe over time there became too many virtual log files. So...

Thanks again...

DBCC SQLPERF(LogSpace) shows that the log is 95% used.

I understand it doesn't run on a schedule, but I would think the next transaction that comes along, it would see...

Thanks Gail for the suggestion. Here are the results:

No active open transactions.

DBCC execution completed. If DBCC printed error messages, contact your system administrator.