virtual memory--should we care?

#1

Hello:

For an XP workstation, Microsoft recommends setting the virtual memory to
1.5 times the amount of RAM.

But, should this also be done on a Windows Server 2003 with SQL Server 2005
with only one hard drive with 3.50 GB of RAM?

And, if so, should both the Minimum and Maximum settings both be set with
this amount of virtual memory?

SQL Programmer (it's just a name)

#2

Are you running 32_bit or 64_bit?

Chris

"SQL Programmer" <SQLProgrammer (AT) discussions (DOT) microsoft.com> wrote

Quote:

Hello:

For an XP workstation, Microsoft recommends setting the virtual memory to
1.5 times the amount of RAM.

But, should this also be done on a Windows Server 2003 with SQL Server
2005
with only one hard drive with 3.50 GB of RAM?

And, if so, should both the Minimum and Maximum settings both be set with
this amount of virtual memory?

SQL Programmer (it's just a name)

#3

32

"Chris Wood" wrote:

Quote:

Are you running 32_bit or 64_bit?

Chris

"SQL Programmer" <SQLProgrammer (AT) discussions (DOT) microsoft.com> wrote in message
news:B20DAA72-D260-4043-9AA3-1C82EE4895E5 (AT) microsoft (DOT) com...
Hello:

For an XP workstation, Microsoft recommends setting the virtual memory to
1.5 times the amount of RAM.

But, should this also be done on a Windows Server 2003 with SQL Server
2005
with only one hard drive with 3.50 GB of RAM?

And, if so, should both the Minimum and Maximum settings both be set with
this amount of virtual memory?

SQL Programmer (it's just a name)

.

#4

Then it certainly does matter. For the benefit of your SQL system you need
to use the 1.5 times. Are you using CLR/linked servers/3rd party products
that get into the MemToLeave (VAS) space? Not having enough virtual memory
affects this area.

Chris

"SQL Programmer" <SQLProgrammer (AT) discussions (DOT) microsoft.com> wrote

Quote:

32

"Chris Wood" wrote:

Are you running 32_bit or 64_bit?

Chris

"SQL Programmer" <SQLProgrammer (AT) discussions (DOT) microsoft.com> wrote in
message
news:B20DAA72-D260-4043-9AA3-1C82EE4895E5 (AT) microsoft (DOT) com...
Hello:

For an XP workstation, Microsoft recommends setting the virtual memory
to
1.5 times the amount of RAM.

But, should this also be done on a Windows Server 2003 with SQL Server
2005
with only one hard drive with 3.50 GB of RAM?

And, if so, should both the Minimum and Maximum settings both be set
with
this amount of virtual memory?

SQL Programmer (it's just a name)

.

#5

Thanks, Chris!

SQL Programmer (it's just a name)

"Chris Wood" wrote:

Quote:

Then it certainly does matter. For the benefit of your SQL system you need
to use the 1.5 times. Are you using CLR/linked servers/3rd party products
that get into the MemToLeave (VAS) space? Not having enough virtual memory
affects this area.

Chris

"SQL Programmer" <SQLProgrammer (AT) discussions (DOT) microsoft.com> wrote in message
news:3B9DCA51-3157-4F4D-8AAC-38BA7FA8A37C (AT) microsoft (DOT) com...
32

"Chris Wood" wrote:

Are you running 32_bit or 64_bit?

Chris

"SQL Programmer" <SQLProgrammer (AT) discussions (DOT) microsoft.com> wrote in
message
news:B20DAA72-D260-4043-9AA3-1C82EE4895E5 (AT) microsoft (DOT) com...
Hello:

For an XP workstation, Microsoft recommends setting the virtual memory
to
1.5 times the amount of RAM.

But, should this also be done on a Windows Server 2003 with SQL Server
2005
with only one hard drive with 3.50 GB of RAM?

And, if so, should both the Minimum and Maximum settings both be set
with
this amount of virtual memory?

SQL Programmer (it's just a name)

.

.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

virtual memory--should we care?

microsoft.public.sqlserver.setup microsoft.public.sqlserver.setup

virtual memory--should we care? - 01-18-2010 , 06:07 PM

Re: virtual memory--should we care? - 01-21-2010 , 10:26 AM

Re: virtual memory--should we care? - 01-21-2010 , 07:53 PM

Re: virtual memory--should we care? - 01-22-2010 , 04:22 PM

Re: virtual memory--should we care? - 01-23-2010 , 11:05 AM