/3GB /Userva=2900 /PAE (AWE Disable) -vs- /3GB /Userva=2900 /PAE (AWE Enable)

Hi Everyone,

I'd like to know the advantages and disadvantages of /3GB /PAE (AWE Disable) and /3GB /PAE (AWE Enable).

Server is Windows 2003 Enterprise is currently configured as /3GB /PAE (AWE Disable) and SQL Server Ent 2000 and AS2000 is up and running. Server has 8GB of physical ram.

Reading the blog: http://blogs.msdn.com/chadboyd/archive/2007/03/24/pae-and-3gb-and-awe-oh-my.aspx

From my understanding "/3GB /PAE (AWE Disable)" will make a 32bit User-Mode Process (say SQLServer or Analysis Services) to address "above 4GB of physical memory" by using its 32-bit Virtual Address Space (3GB because of /3GB switch) as a pointer mapping function to access data that is stored in the "above 4GB of physical memory".

This will allow the OS more physical memory space for storing "swapping" data instead of having to page this data to disk.

Now for "/3GB /PAE (AWE Enable)", this is the "above statements" plus, the capability of the process (SQL Server) to reserve the memory outside it's VAS for storage.

So in summary,
"/3GB /PAE (AWE Disable)" will make the OS use the additional memory <4GB for "paging/swapping" purposes, due to the VAS limitation of 3GB for User-Mode process.
and
"/3GB /PAE (AWE Enable)" will make SQLServer "reserve in advance" w/ agreement with the MAX Memory setting, memory above 4GB.

So if this is all true, I'd like to get opinons on the advantages and disadvantages of enabling or disabling AWE. Noting that Analysis Services has a Max Memory of around 2.5GB and Min Memory of around 2.0GB and SQL Server has Min Memory of 0 and Max Memory of 3.5GB (to be increased? - even w/o AWE?)

Thanks,
Henry