August 20, 2009 at 7:58 am
I am upgrading a sql 2005 ent edit box from 32 bit to 64 bit. Doesn't the boot.ini reference and awe become not needed when going to the 64 bit version
August 20, 2009 at 8:01 am
Neither PAE or AWE have any effect and are not needed with 64-bit.
CEWII
August 20, 2009 at 8:14 am
Elliott W (8/20/2009)
Neither PAE or AWE have any effect and are not needed with 64-bit.CEWII
As in even though they are selected by default they dont do any thing (on or off)
Adam Zacks-------------------------------------------Be Nice, Or Leave
August 20, 2009 at 9:43 am
Pretty much.
http://msdn.microsoft.com/en-us/library/ms190673(SQL.90).aspx
"AWE is not needed and cannot be configured on 64-bit operating systems."
CEWII
August 20, 2009 at 12:23 pm
I think you need to Enable AWE, in SQL, on 64-bit systems if you want to use lock pages in memory.
There is an issue in MS SQL 2008 SP1 with lock pages in memory and you'll need to apply cumulative update 2 for SP1 in order to fix that.
August 20, 2009 at 2:39 pm
on 64 bit sql server systems you only need to apply the lock pages in memory policy to the sql server service account, dont touch the AWE check box it doesnt do anything.
Bear in mind that SQL Server 2005 Std ingores the lock pages in memory policy, you need SP3 CU4 for Std edition to use this local policy
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply