Warning: Constant WP_TEMP_DIR already defined in /var/www/html/blogs/glenn/wp-config.php on line 94

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/glenn/wp-config.php:94) in /var/www/html/blogs/glenn/wp-includes/rest-api/class-wp-rest-server.php on line 1902

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/glenn/wp-config.php:94) in /var/www/html/blogs/glenn/wp-includes/rest-api/class-wp-rest-server.php on line 1902

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/glenn/wp-config.php:94) in /var/www/html/blogs/glenn/wp-includes/rest-api/class-wp-rest-server.php on line 1902

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/glenn/wp-config.php:94) in /var/www/html/blogs/glenn/wp-includes/rest-api/class-wp-rest-server.php on line 1902

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/glenn/wp-config.php:94) in /var/www/html/blogs/glenn/wp-includes/rest-api/class-wp-rest-server.php on line 1902

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/glenn/wp-config.php:94) in /var/www/html/blogs/glenn/wp-includes/rest-api/class-wp-rest-server.php on line 1902

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/glenn/wp-config.php:94) in /var/www/html/blogs/glenn/wp-includes/rest-api/class-wp-rest-server.php on line 1902

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/blogs/glenn/wp-config.php:94) in /var/www/html/blogs/glenn/wp-includes/rest-api/class-wp-rest-server.php on line 1902
{"id":877,"date":"2014-04-09T07:19:59","date_gmt":"2014-04-09T14:19:59","guid":{"rendered":"http:\/\/3.209.169.194\/blogs\/glenn\/?p=877"},"modified":"2018-11-13T10:52:27","modified_gmt":"2018-11-13T18:52:27","slug":"recommended-intel-processors-for-sql-server-2014-oltp-workloads","status":"publish","type":"post","link":"https:\/\/www.sqlskills.com\/blogs\/glenn\/recommended-intel-processors-for-sql-server-2014-oltp-workloads\/","title":{"rendered":"Recommended Intel Processors For SQL Server 2014 OLTP Workloads"},"content":{"rendered":"

If you are in the process of evaluating and selecting the components for a new database server to run an OLTP workload on SQL Server 2014 Enterprise Edition, you have several initial choices that you have to make as a part of the decision process. First you have to decide whether you want to go with an AMD-based server or an Intel-based server. Unfortunately, I cannot recommend that you use an AMD processor for SQL Server 2012\/2014 OLTP workloads, due to the combination of low single-threaded performance and high SQL Server licensing costs (even with the 25% discount from the SQL Server 2012 Core Factor Table). <\/p>\n

Next, you need to decide on the server socket count, which means choosing a single-socket, dual-socket, quad-socket, or eight-socket server (at least in the commodity server market). After you choose the socket count, you need to decide exactly which of the available processors you want to use in that model server. Looking at the choices for several current model servers from the major system vendors, you will discover that you will have to pick from around 15-20 different specific processors. All of this can be a little overwhelming to consider, but I urge you to do some research, and to choose carefully. Letting someone else pick your processors, who may not be familiar with SQL Server 2012\/2014 licensing and the demands of different database workload types, could be a lasting, costly mistake. <\/p>\n

With the core-based licensing in SQL Server 2012\/2014 Enterprise Edition, you need to pay closer attention to your physical core counts, and think about whether you are more concerned with extra scalability (from having more physical cores), or whether you want the absolute best OLTP query performance (from having a processor with fewer cores but a higher base clock speed from the same processor generation). Unlike in the good old days of SQL Server 2008 R2 and older, having more physical cores will cost you more for your SQL Server 2012\/2014 Enterprise Edition licensing costs. You really need to think about what you are trying to accomplish with your database hardware. For example, if you can partition your workload between multiple servers, then you could see much better OLTP performance from using two dual-socket servers instead of one quad-socket server. <\/p>\n

So, here are the Intel processors that I recommend in mid-April 2014 for OLTP workloads, with their high-level specifications and some commentary. <\/p>\n

One-Socket Server (High Capacity)<\/strong> <\/p>\n

Intel Xeon E5-2470 v2<\/a> (22nm Ivy Bridge-EN) <\/p>\n