<div>
First of all: You need to pay for nothing. The memory has its cost and it will lead to more power consumption. <br />
<br />
As Matthew wrote you're risking to get issues for nothing. Especially depending on the server it requires downtime and some hardware fiddling (cooldown time of the disks before moving the case) which also has its own risks of getting hardware troubles.<br />
<br />
It only would make sense, when you already have a commited schedule that your upgrade the OS in the near future AND your co-worker has to open the server case anyway.
</div>


<div>
no it will not cause issues,<br />
usually the question is whether adding additional memory will solve the issue at hand.
</div>


<div>
Thanks to all of you!<br />
I agree with not taking risks. &nbsp;Things are currently running okay.<br />
We probably won't upgrade for 6-12 months.<br />
However, my coworker is pretty bent on need memory upgraded for SQL.<br />
I'll see if I can reason.<br />
Our main SQL server (ERP server) with the biggest job is already maxed.<br />
We have two other servers with SQL, while do relatively light weight tasks and already has 16GB.<br />
The other is has moderate tasks and has 8GB, but there is a hardware limitation (older tech) of 12GB.<br />
We do have one remaining server with SQL that only has 4GB and could use more. &nbsp;It is used for LANDesk, which is our desktop management tool.
</div>


<div>
sql will consume as much memory as there is available through the OS.<br />
your database size will answer whether the performance might improve with additional memory.<br />
<br />
this may help during the upgrade cycle to choose the version of os suitable for your business line.
</div>


<div>
<blockquote>
However, my coworker is pretty bent on need memory upgraded for SQL.
</blockquote>
<br />
Just throwing memory at a problem is not sufficient. When the SQL Server needs more memory, then it must be justified by facts. Especially as it requires a new OS version.<br />
<br />
Depending on your SQL Server version, you're already running an older Windows server, this means not only more memory and a new OS, but also a new SQL Server version.<br />
<br />
While I also advocate for being as actual as possible, this is nothing you do without planning.
</div>


<div>
@Arnold: SQL Server will only consume as much memory as configured. The min and max memory *should* be configured always to a feasible amount with enough memory remaining for the OS.
</div>


<div>
yes, I am aware of the min/max option in sql, the limit detailed in the question is the Memory available to and by the OS based on the OS version. And seems to be the thrust of the question. For an SQL server, one would allocate as much memory as there is available to SQL.
</div>


<div>
ste5an,<br />
Thanks. &nbsp;You have hit on my main concern exactly. &nbsp;My coworker wants to add memory and update the OS service packs and upgrade the SQL versions with hardly any planning or analysis. &nbsp;This scares me. &nbsp;I am asking these questions so I can reason with him appropriately.
</div>


<div>
<div class="content wysiwyg-content">
We are upgrading the memory in some of our servers. &nbsp;The hardware will support over 64GB of RAM. &nbsp;The OS is Server 2008 R2 &quot;Standard&quot; 64-bit. &nbsp;According to Microsoft, &quot;Standard&quot; can only utilize 32GB. &nbsp;If my co-workers want to go ahead and install more than 32GB, in anticipation of a future upgrade to &quot;Enterprise&quot;, or whatever reason, will this cause issues, like the OS not starting?
</div>
</div>


We are upgrading the memory in some of our servers.  The hardware will support over 64GB of RAM.  The OS is Server 2008 R2 "Standard" 64-bit.  According to Microsoft, "Standard" can only utilize 32GB.  If my co-workers want to go ahead and install more than 32GB, in anticipation of a future upgrade to "Enterprise", or whatever reason, will this cause issues, like the OS not starting?

For Microsoft Server &quot;Standard&quot; editions, will installing more 32GB of memory cause issues?

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.

Microsoft Legacy OS

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

For Microsoft Server &quot;Standard&quot; editions, will installing more 32GB of memory cause issues?

For Microsoft Server "Standard" editions, will installing more 32GB of memory cause issues?