July 28, 2011 at 6:10 am
hi
i am setting up a test system with sql 2005 std sp 2 on server 2008 ent which has 6gb of ram..
i know from previous version i need to add a 3gb switch to the boot record to allow sql to utilise extra memory - in server 2008 from what i have read i am to run BCDEDIT /SET PAE ForceEnable
is that correct?
can anyone advise me on a script that will show me the memory available for sql to prove this has worked?
cheers
mal
July 28, 2011 at 6:21 am
found it!
SELECT * FROM sys.dm_os_performance_counters
WHERE counter_name IN ('Target Server Memory (KB)','Total Server Memory (KB)')
which shows it worked ! 🙂
July 28, 2011 at 6:25 am
32 bit or 64 bit? (OS and SQL)
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
July 28, 2011 at 6:30 am
both 32 bit
July 28, 2011 at 7:54 am
I would recommend that you don't use /3GB here, all that will let SQL do is access 3GB of memory instead of 2. The memory above the 4GB boundry will still be unavailable.
Rather use AWE, the /PAE switch if it's necessary (I don't think it is on Server 2008) and then set SQL's max memory to 5GB.
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
July 28, 2011 at 9:15 am
Why SP2 ? SP4 has been out a while. At least go to SP3 for all the big fixes.
July 28, 2011 at 9:18 am
yea ill upgrade to sp3 once im happy with current setup - the install discs just are sp 2
is it just bug fixs or are there any decent new features?
July 28, 2011 at 9:49 am
Bug fixes (including some nasties). It's generally frowned on for a service pack to include new features. MS took a lot of flack for that with 2005 SP2.
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
July 28, 2011 at 9:57 am
any bug fixs that could improve overall performance?
July 28, 2011 at 9:59 am
malachyrafferty (7/28/2011)
any bug fixs that could improve overall performance?
July 28, 2011 at 10:01 am
malachyrafferty (7/28/2011)
any bug fixs that could improve overall performance?
For SQL, no. For you own code, it's called tell at the developers to fix their mess.
Bad query performance is seldom a SQL bug (as in really, really, virtually never seldom). It's from poorly written queries and/or poor indexing.
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
July 28, 2011 at 10:03 am
cheers ninja - we actually are running pretty decently - i was just wondering if there was anything that maybe would give us an unexpected boast in sp3
July 28, 2011 at 10:07 am
malachyrafferty (7/28/2011)
cheers ninja - we actually are running pretty decently - i was just wondering if there was anything that maybe would give us an unexpected boast in sp3
Sure give me a call and I'll do a server checkup. I promess I'll make more of an impact than SP3 ;-).
Viewing 13 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply