First, AWE is not an option on x64 hardware because it is not needed. You don't have to check the box to enable it - it is not recognized on x64 systems.
Yes, there is an option build a Win x64 server with SQL x64. It's even available in SQL 2008 x64. Heres the setting of a win2008 x64 with SQL x64:
http://207.231.94.134/x64AWE.jpg
If it's there and selectable, one has to ask the question why is it even there if you say it's not. Do you know something we dont? If so let us know.
Second, for a dedicated database server there is no reason to set a minimum memory amount. Setting the minimum to 12GB and the maximum to 14GB running SQL Server 2005 Standard Edition (x64) will almost certainly cause memory pressure on the system.
Exactly what memory pressures are you referring to? Other OS Apps? If it's just a dedicated DB server there's nothing more that should be running. So are you also saying that letting SQL dynamically self allocate RAM pages/addresses on a per needed bassis more efficient than telling SQL this is your starting huge pool of memory but you can grab up to 2 GB more if needed?
Third, SQL Server 2005 Standard Edition (x64) cannot lock pages in memory. Setting the policy is a good idea, but it will not make any difference using this edition. There is a patch on the way that will change this behavior but it is not out yet.
Segment of original post: "I installed windows 2003 enterprise edition 64 bit ". This is what I was referring to. Should've more specific. Personally I thought that this was strictly an OS function and not a SQL function. It is only a setting in the OS and there is nothing in SQL to set this. One would think that if the credentials SQL was running on would still lock. Can you elaborate in this? I would like to know as I have never heard of this.
As for the Bosst SQL, you're right...lol, WTF was I thinking. :w00t:
