A. A. (2/15/2013)
You and I both know they didn't squeeze more money from you to lift the 32 bit OS limits. We paid good money for SQL that rightly got around it.
*sigh* The facility to get around the 32 bit limits was built into the OS. Any program that could access the AWE APIs (OS-level APIs) could access memory above the 4GB boundary. Hence it was not SQL that was evading an OS limitation, it was SQL using the OS-provided APIs to access memory above what a 32-bit process can directly address
Anyway, it's not evading to expect software you bought that intelligently helped you overcome OS memory limits before to continue to do do now that its 64 bit and easily could.
Again, the 32 bit limit was not an OS limitation. The OS was what provided the ability for 32 bit processes to access memory above the 4 GB boundary.
Now, if you want to continue to believe the opposite, be my guest. This is not MS fandom, this is fact, you can go and read up on memory architecture and memory access and it'll tell you just the same.
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