Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
tfountain
Constraint Violating Yak Guru
491 Posts |
 Posted - 2008-11-04 : 17:11:33
|
We have an active/passive cluster (SQL 2005 Enterprise SP2). Recently we retired the passive server, made the active the passive and added a newer server as the active (a pretty standard swap). Since then, one job that runs every night fails with the errorThere is insufficient system memory to run this query The job cycles all databases and issues the command:DBCC CHECKDB(<dbname>) WITH NO_INFOMSGS Now this is the only thing that fails with this error period, everything else is running smoothly. The job runs for approximately 30 minutes and fails.Any suggestions on what can cause this type of error? Running SQL Server 2005 Enterprise SP2 on Windows 2003 Enterprise Server (x32). |
|
|
saurabhsrivastava
Posting Yak Master
216 Posts |
Posted - 2008-11-05 : 12:39:36
|
| This forum might help you |
 |
|
|
saurabhsrivastava
Posting Yak Master
216 Posts |
Posted - 2008-11-05 : 12:40:39
|
| FYI- when you run check DB it takes snapshot of DB and in case of big database it tries to grab big chunks of memory |
|
|
|
tfountain
Constraint Violating Yak Guru
491 Posts |
Posted - 2008-11-06 : 10:20:13
|
quote:
Originally posted by saurabhsrivastava
This forum might help you
Unless you where stating *this* formum (SQL Team), I think you omitted a link. |
|
|
|
saurabhsrivastava
Posting Yak Master
216 Posts |
|
|
tfountain
Constraint Violating Yak Guru
491 Posts |
Posted - 2008-11-10 : 14:27:46
|
| Yes, I did find that link in my initial searches. This did not yield anything useful for me. I think I might just run a profile while this statement is running to see if that sheds any light on the error. It does happen on the same database every time- I was able to verify that and it is definitely reproducible. |
|
|
|
saurabhsrivastava
Posting Yak Master
216 Posts |
Posted - 2008-11-10 : 22:48:06
|
| I know when you run checkdb it flushes the procedure cache. This is a bug. It might be possible that in order to bring lot of data again in cache it generates memory error. |
|
|
|
|
|
|
...insufficient system memory to run this query...