I don't know about the other trace flags and priorities/precidence.

The fix came directly from Microsoft Support and didn't mention trying anything else first.

The solution worked brilliantly and keeps those cached...

July of 1924?

~BOT

I'm pretty sure you can add files on-the-flly but not remove them

you verify with this:

http://msdn.microsoft.com/en-us/library/ms190326.aspx

~BOT

Set another @datetime variable in your calling code to be the date you want and pass that to the sproc instead of anything with getdate() in it.

You could also set...

I'm sure you have your reasons, but it seems strange to me that everything is binary, even though column names indicate other data types.

to answer your question:

SELECT...

Exactly.

Your other SQL Instances are having memory stolen from them by the OS which is under memory pressure.

My favorite SQL Server memory article of all time says that

SQL Server 2005...

You're probably right about logging to a file. not much can go wrong there.

I suppose if you log to a table instead of a file anything that would prevent...

Best bet is to build the environment based on need.. share the instances if possible because each instance running can load the OS with as much as 1.5 GB memory...

For posterity it turned out to be an issue with cached user permissions because the vendor code uses too much ad-hoc SQL

This Article sums up the issues nicely.

the fix is...

In my experience, setting a database to trustworthy then creating a proc 'with execute as sa' will allow the executor of the proc to see everything that sa can see.

Maybe...

Sorry,

I fell asleep at the wheel on this thread.

The checkpoint process should always be running somewhere, or in the state 'checkpoint wait'

There are many activities that automatically initiate a checkpoint

http://msdn.microsoft.com/en-us/library/ms188748(SQL.90).aspx

The...

Don't wait around too long.

IF a checkpoint is stuck that means you can't get a backup. can't run a dbcc, etc.

I've had this happen once, tried everything and...

looks pretty pointless to me... snooze that one.

33% isnt' that busy. If it's interfering with paging (high page in/out rates) then you may have a problem.

... not enough RAM,...

All you need to do is change the maximum file size on the mdf and ldf files... that is unless your volume where those files reside is full. If...

Jonathan is probably right.

If you're using spotlight, drill into the memory counters and see if the proc cache is being pinched by any of the other memory areas (lock, object...