SQL Server – Windows 32 bit – SQL Server v2014

Background

Reviewing Memory Utilization on one of our boxes.

 

Troubleshooting

Windows Version

Control Panel

System

Image

Explanation
  1. Windows Server 2008 Enterprise

Performance Monitor

Metrics

Metrics – [ SQL Server Instance ] – Memory Manager

Image

Textual

  1. Stolen Server Manager ( KB ) :- 448,400.000
  2. Target Server Memory ( KB ) :- 1,531,904.00
  3. Total Server Memory ( KB ) :- 1,516,648.00

 

SQL Server

Metadata

@@version

Image
Textual

Microsoft SQL Server 2014 (SP2-CU6) (KB4019094) – 12.0.5553.0 (Intel X86)
Jun 28 2017 14:05:44
Copyright (c) Microsoft Corporation
Enterprise Edition: Core-based Licensing on Windows NT 6.0 <X86> (Build 6002: Service Pack 2) (VM)

 

Explanation
  1. We are running MS SQL Server 2014 / SP2 ( CU-6 )
  2. Enterprise Edition: Core-based Licensing on Windows NT 6.0 <X86>
    • Windows NT 6.0
      • Windows Server 2008
        Link
    • X86
      • 32 bit OS

Engineering

In terms of Engineering, can we do more.

Microsoft

AWE

The “awe enabled” SQL Server feature is deprecated.
Link

Summary

In Microsoft SQL Server 2008 R2, the configuration option, awe enabled, is deprecated. In the next version, Microsoft SQL Server 2012, this configuration option and the feature that uses this configuration option are removed from the product.

Therefore, when you upgrade from SQL Server 2008 R2 to the next version of SQL Server, you cannot use more memory than what the virtual address space limits in 32-bit instances of SQL Server. If you must have more memory for this instance of SQL Server, then you have to migrate to a 64-bit instance of SQL Server.

Operating System & SQL Server v2012+ Max Memory

SQL Server and operating system settings Maximum amount of memory used by SQL Server
32-bit SQL Server on 32-bit OS 2 GB
32-bit SQL Server on 32-bit OS with /3G boot option 3 GB
32-bit SQL Server on 64-bit OS 4 GB

Closing

As always keep in mind what your end goal is and what engineering constraints are holding you back.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s