SQL2005 64-BIT Just Installed...now what?

Question

SQL2005 64-BIT Just Installed...now what?

rew-370421

Hall of Fame

Points: 3640
More actions
January 21, 2010 at 12:18 pm

#137511

I just installed SQL2005 Std 64BIT on a W2K3 64BIT sp2 O/S. It has 2 CPUs and 8GB of RAM.
Are there any SQL Server configurations or changes I should make?
I'm confused about this "lock pages in memory" setting (is it enabled/disabled) and if it should be addressed or not?
Within SQL2005
This is what the MEMORY setting is on the GENERAL Page:
Memory 7935 (MB)
This is what the Min/Max settings are on the MEMORY Page:
the Minimum server memory (in MB) = o
the Maximum server memory (in MB) = 2147483647
How do I or should I configure the SQL Memory?
Do I do anything with "lock pages in memory"?
thanks!

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 1

Only suggestion I will make, set max memory to 6144 MB. This will leave 2 GB for the OS. Depending on whatever else you may be running on the server, you may consider lowering the max memory setting to something less than that I suggest.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 2

Standard edition ignores locked pages if you're below a certain patch level. SP3 + some cumulative update. Can't recall exactly which one (google is your friend here)

Setting max memory is not optional on 64 bit. If you don't, SQL will take over and cause problems, especially if there's other stuff running on the machine.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 3

GilaMonster (1/21/2010)
Standard edition ignores locked pages if you're below a certain patch level. SP3 + some cumulative update. Can't recall exactly which one (google is your friend here)
Setting max memory is not optional on 64 bit. If you don't, SQL will take over and cause problems, especially if there's other stuff running on the machine.

Yes, I thought I had set max memory on two of my recent x64 SQL Server 2008 EE installs. Sys Admin emailed me and said the OS was starving on both blades. Oops, quickly fixed.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 4

I've done it on my x64 desktop. Ran a simple update. Everything stopped responding, including OS. Not pretty.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

rew-370421 Hall of Fame Points: 3640 More actions · Answer 5

Lynn / Gail

thanks very much for the quick response. I've already made the change!