Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I've inherited a server that has 8 previously installed instances of SQL Server 2005 Developer Edition. The instance I am working with is SQL Server 2008 Express.

All of the Developer Edition instances are disabled as well as their corresponding SQLAgents. It was requested that nothing be uninstalled.

We have seen a memory error running DBCC CHECKDB on the new database:

Msg 8921, Level 16, State 1, Line 1 Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors. Msg 701, Level 17, State 123, Line 1 There is insufficient system memory in resource pool 'internal' to run this query.

Could these previously installed instances affect memory usage of the active instance even though they are disabled?

share|improve this question
    
Can you post the error? –  K. Brian Kelley Jul 3 '10 at 20:49
    
Error posted. Thx. –  8kb Jul 3 '10 at 21:20

5 Answers 5

up vote 1 down vote accepted

No. No services/binaries running = no memory usage.

What DBCC errors did you get?

share|improve this answer
    
CheckDB failed: insufficient system memory in resource pool. –  8kb Jul 3 '10 at 21:23

If an app isn't running, it doesn't consume memory. But folks who do things like install 8 SQL instances likely screwed up all sorts of other stuff on the server.

share|improve this answer
    
Could the previously installed instances somehow affect the amount of memory the new instance was allocated on installation? –  8kb Jul 3 '10 at 21:21
    
No, If not activated it does not run it does only comsume space... on the discs. –  TomTom Jul 4 '10 at 17:32

Check if the max server memory was not reduced on each instance. See Server Memory Options.

share|improve this answer

If the max memory in your non-running instances is set to some high value, the instance you are currently working on may not be able to use all the memory. As Resmus said above you can reduce it or configure it so that SQL will allocate its memory requirments dynamically.

share|improve this answer

Seems this is memory handling related problem of your SQL Server 2008 instance and nothing related to shutdowned SQL 2005 instances. Try add -g384 switch to SQL Server service startup parameters...

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.