December 11, 2002 at 10:13 am
We had Sql Server standard edition on a Windows 2000
platform. The server had 4 CPU's and 4 GB of memory. We
wanted to increase the memory to 8 GB. Hence we detached
the databases on the server, installed Windows Advanced
server and SQL Server Enterprise edition. We did add
the /3GB and /PAE to boot.ini. We then re-attached the
databases.
However, the run time of the jobs before adding the
memory is almost half of what it is after adding the
memory. I am looking for help in troubleshooting this
problem. Thanks in advance for your help.
December 11, 2002 at 10:32 am
You probably made other configuration changes to your server that are more likely to impact throughput than just adding memory.
What else changed? A new OS is fraught with peril and is a large change in an of itself.
December 11, 2002 at 10:35 am
How much memory have you given SQL? With PAE, you don't need the /3GB switch. You still want 2GB for the OS, then give 6GB to SQL, assign this as the min and max. If you have other apps, then you can alter this.
Steve Jones
December 11, 2002 at 12:21 pm
quote:
How much memory have you given SQL? With PAE, you don't need the /3GB switch. You still want 2GB for the OS, then give 6GB to SQL, assign this as the min and max. If you have other apps, then you can alter this.Steve Jones
http://www.sqlservercentral.com/columnists/sjones
December 11, 2002 at 1:00 pm
quote:
quote:
How much memory have you given SQL? With PAE, you don't need the /3GB switch. You still want 2GB for the OS, then give 6GB to SQL, assign this as the min and max. If you have other apps, then you can alter this.Steve Jones
http://www.sqlservercentral.com/columnists/sjones
December 11, 2002 at 2:45 pm
Do you have a question? Not sure what you mean.
Steve Jones
December 12, 2002 at 8:15 am
We just scaled-up our db server, and went to 4 1.6 ghz processors (up from 750 mhz) with 8 gigs RAM (up from 4)
I did both PAE and 3GB and set SS Memory *Fixed* to 6 gigs. Works fine. Then I gave SS 6.25...works fine. Now I'm at SS with 6.5...works fine.
Before the 8 gigs, when there were only 4 gigs, the /3GB switch gave OS 1 and SS 3. Since SS worked ok with 1 before I figured I'd test the limit.
An extra gig of SS memory is alot of cache.
What needs to happen when you turn PAE on is to set AWE in SS on and then set your memory values since SS will not dynamically allocate memory with AWE on and over 4 gigs present. That could be the source of your performance problem.
PlanetJam Media Group
PlanetJam Media Group
December 12, 2002 at 12:21 pm
You need to enable awe on server using
sp_configure, also task manger counter regarding memory is not correct use perfmon.
Make sure memory configuration on server is set to fix value.
Can not use dynamic memory
December 13, 2002 at 10:46 am
With reference to what sam said, if you don't limit the memory for SQL Server after enabling AWE, SQL Server will take all the memory leaving just 128 MB for your OS.
The folloing link might be helpful.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy