Dennis Post (3/3/2014)

---

Is this a 32 bit system? The memory pools used by SQL Server in a 32 bit system sometimes needed help. Especially if you were moving around a lot of BLOBs, or CLR objects.

Yes, this is a 32 bits system, no BLOBs or CLR though. The errors occur on a server with build 9.0.3042 (SP2). I am looking to upgrade this server, but it's a 24/7 server with multiple DBs.

Is your application using Connection Pooling ?

Nope. VB6. Each appplication just has one connection. If multiple DBs are involved, one connection per DB.

Connections are opened when the applications start, closed when the applications close. Users run the applications in a Terminal Server 2003 32bit environment. Because these connections are open for so long, I was wondering what resources they are holding on to and if they are the cause of these errors.

Did you capture any problematic queries that run during that time ? How abt your daily Maintenance Plans ? Are they running successfully ..

There is a job that runs every 2 hours from 8:23 am till midnight. If it's this job that's causing the errors then it's unusual that the errors aren't happening all the time. Anyway, I shortened the schedule for the job to stop well before the errors start occuring. The other jobs that are failing are log backups.

I'll start collecting those other counters you mentioned.

Thanks for the help guys!!