January 8, 2010 at 8:37 am
Lynn Pettis (1/8/2010)
Krasavita (1/8/2010)
Is each instance contains their own RAM?It depends,
PLEASE ANSWER THE FOLLOWING:
What is the configuration of the development server (total server memory, disk drives (raid type or not, etc)? How are the instances configured (min/max memory, etc)?
Try again, that is only a small piece of what was requested.
Need to know the configuration of the server AND each of the instances.
Based on what you just posted, the instances are probably fighting each other for the servers existing memory.
January 8, 2010 at 9:06 am
I know max 2147483647 MB, for each instanse, how much should I cut down too?
January 8, 2010 at 9:14 am
Krasavita (1/8/2010)
I know max 2147483647 MB, for each instanse, how much should I cut down too?
How much memory does the physical server have and is it x86 or x64?
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
January 8, 2010 at 9:21 am
we are adding 4G RAM now. I have 2 instanses that I don't need, how can I remove them?
January 8, 2010 at 9:23 am
x86
January 8, 2010 at 9:30 am
Krasavita (1/8/2010)
we are adding 4G RAM now. I have 2 instanses that I don't need, how can I remove them?
Okay, you are adding 4GB, so how much total??
January 8, 2010 at 9:48 am
Krasavita (1/8/2010)
What is the configuration of the development server (total server memory, disk drives (raid type or not, etc)? How are the instances configured (min/max memory, etc)?How can I check these, I can't get to the server it is timing out on me.Can I run someting from query analyzer
Can you please post the results for the below query..
exec xp_msver
Thanks..
The_SQL_DBA
MCTS
"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
January 8, 2010 at 9:50 am
You can shut down the services for the two unneeded instances in the Control Panel | Servers, and set their startup to "manual".
January 8, 2010 at 9:51 am
I think you'd have much more luck starting with an x64 machine.
At a bare minimum, 9 * 1GB for the instances + 2 GB for the OS.
And each instance needs to be limited for RAM also.
As Lynn also points too - disc is also a big part of your setup.
Greg E
January 8, 2010 at 9:55 am
object_name counter_nameinstance_namecntr_valuecntr_type
SQLServer:Memory Manager Target Server Memory (KB) 130740065792
SQLServer:Memory Manager Total Server Memory (KB) 2278465792
January 8, 2010 at 9:57 am
IndexNameInternal_ValueCharacter_Value
1ProductNameNULLMicrosoft SQL Server
2ProductVersion5898249.00.3068.00
3Language1033English (United States)
4PlatformNULLNT INTEL X86
5CommentsNULLNT INTEL X86
6CompanyNameNULLMicrosoft Corporation
7FileDescriptionNULLSQL Server Windows NT
8FileVersionNULL2005.090.3068.00
9InternalNameNULLSQLSERVR
10LegalCopyrightNULL© Microsoft Corp. All rights reserved.
11LegalTrademarksNULLMicrosoft® is a registered trademark of Microsoft Corporation. Windows(TM) is a trademark of Microsoft Corporation
12OriginalFilenameNULLSQLSERVR.EXE
13PrivateBuildNULLNULL
14SpecialBuild201064448NULL
15WindowsVersion2483819575.2 (3790)
16ProcessorCount11
17ProcessorActiveMask100000001
18ProcessorType586PROCESSOR_INTEL_PENTIUM
19PhysicalMemory38393839 (4025954304)
20Product IDNULLNULL
January 8, 2010 at 9:58 am
Greg Edwards-268690 (1/8/2010)
I think you'd have much more luck starting with an x64 machine.At a bare minimum, 9 * 1GB for the instances + 2 GB for the OS.
And each instance needs to be limited for RAM also.
As Lynn also points too - disc is also a big part of your setup.
Greg E
Unless there are 4-8 processor cores, context switching alone is going to be a performance problem, and the memory requirements for x64 are greater than for x86 which is why I asked about platform.
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
January 8, 2010 at 10:04 am
Krasavita (1/8/2010)
object_name counter_nameinstance_namecntr_valuecntr_typeSQLServer:Memory Manager Target Server Memory (KB) 130740065792
SQLServer:Memory Manager Total Server Memory (KB) 2278465792
This is telling you that this instance needs 1.3GB of RAM, but is only getting 22MB. You need to set your maxservermemory on every instance to divide up the memory across the instances, leaving 1GB for the OS. With your current setup that would be less than 300MB RAM per instance which is less than the default VAS Reservation (384MB) for a x86 instance with 1 CPU.
Your other problem is going to be 1CPU. All of the instances are going to be fighting for execution time and will pre-empt each other for scheduling time on the CPU. SQL has its own built in Operating System designed to prevent pre-emptive scheduling and context switching from occuring. You have multiple compounded problems with your hardware being to small for what you are trying to do.
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
January 8, 2010 at 11:09 am
I stoped 4 instances that we are not using and changex max settings and now I have these:
counter_nameinstance_namecntr_value
Target Server Memory (KB) 1497560
Total Server Memory (KB) 22784
Thank you very much for your help
This is development server, I recommended to switch to 64 bit how many processors I need?
January 8, 2010 at 11:18 am
Oh, I didn't change max memory for my maine instanse, do I need it? I only changed max memory for all 9 instansases
Viewing 15 posts - 16 through 30 (of 55 total)
You must be logged in to reply to this topic. Login to reply