Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Teams
Q&A for work
Connect and share knowledge within a single location that is structured and easy to search.
Learn more about Teamsx86 processes with the LargeAddressAware bit set (like sqlservr.exe) get a full 4 GB VAS for themselves. Enabling AWE (on Enterprise Edition OS and Enterprise Edition SQL editions that support it) allows the SQL server instance to map extra pages (up to 64GB) in and out of its VAS and use them for the buffer pool.
That being said, x86 is a dead end and you should switch to an x64 instance ASAP.
x86 processes with the LargeAddressAware bit set (like sqlservr.exe) get a full 4 GB VAS for themselves. Enabling AWE (on Enterprise Edition OS and Enterprise Edition SQL) allows the SQL server instance to map extra pages in and out of its VAS and use them for the buffer pool.
That being said, x86 is a dead end and you should switch to an x64 instance ASAP.
x86 processes with the LargeAddressAware bit set (like sqlservr.exe) get a full 4 GB VAS for themselves. Enabling AWE (on OS and SQL editions that support it) allows the SQL server instance to map extra pages (up to 64GB) in and out of its VAS and use them for the buffer pool.
That being said, x86 is a dead end and you should switch to an x64 instance ASAP.
x86 processes with the LargeAddressAware bit set (like sqlservr.exe) get a full 4 GB VAS for themselves. Enabling AWE (on Enterprise Edition OS and Enterprise Edition SQL) allows the SQL server instance to map extra pages in and out of its VAS and use them for the buffer pool.
That being said, x86 is a dead end and you should switch to an x64 instance ASAP.
