This server has about 50 jobs on it some run as frequently as every 10 minutes.

The job didn't fail it simply didn't execute at all. There is no entry for the time it was suppose to execute in the job history at all.

There is plenty of job history plus I archive all job history off to another server.

The job hasn't be modified since it was installed.

SQL Agent was running the whole time. We get alerts immediately if the agent is down from our nagios box.

We have...

No not yet.

This job has run successfully except for the one day it skipped. It ran successfully today at its normal time. We can't find any reason for it...

Yeah,

I walked through all of it and so did someone else just to make sure I didn't miss something.

I hate writing a monitor for all the jobs on all...

Thanks for the feedback! I'll make the changes and post them back up.

Wes

Gail,

I am aware of what the best practice is for memory management. Quoting rote and verse from one of Ken's books buys you no points with me. You made the...

SQL Server uses as much memory as it needs or that is available. It caches database data pages for performance reasons. Unless you are having a problem with the server...

LDF is a transaction log data file. The log is sequential and doesn't benefit from additional files other than space constraints.

SQL Server uses as much memory as it needs or has available to it as cache. There may not be anything wrong at all with SQL Server. If you don't...

http://support.microsoft.com/kb/832524

GilaMonster (8/8/2008)

---

Do not use either /3GB or /userva if you are using AWE. You're asking for a unresponsive server.

You do need to enable AWE if you want SQL to use...

7 days of backups allows you to catch around 90% of all errors most of them due to human errors.

to get much better than that 21 days is the next...

I would also look at context switches if this is a extremely busy server with lots of connections and small queries. If it is in say the millions you may...