Some Quick Comparative CrystalDiskMark Results

A few weeks ago, I built a new Intel Skylake desktop system that I am going to start using as my primary workstation in the near future. I have some details about this system as described in Building a Z170 Desktop System with a Core i7-6700K Skylake Processor. By design, this system has several different types of storage devices, so I can take advantage of the extra PCIe bandwidth in the latest Intel Z170 Express chipset, and do some comparative testing.

The latest addition to the storage family is a brand new 512GB Samsung 950 PRO M.2 PCIe NVMe card that just arrived from Amazon yesterday afternoon. As of now, here is the available storage in this system:

  1. (2) 512GB Samsung 850 PRO SATA III SSDs in RAID 1 (using the chipset RAID controller)
  2. (1) 512GB Samsung 950 PRO M.2 PCIe 3.0 NVMe card in an Ultra M.2 PCIe 3.0 x4 slot
  3. (1) 400GB Intel 750 PCIe NVMe card in a PCIe 3.0 x16 slot
  4. (1) 6TB Western Digital SATA III hard drive in a SATA III port

Since I have an NVidia GeForce GTX 960 video card in one of the PCI 3.0 x16 slots, both that slot and the PCI 3.0 x16 slot that the Intel 750 is using will go down to x8 (which means 8 lanes instead of 16 lanes). The Intel Z170 Express chipset supports 26 PCIe 3.0 lanes, so you need to think about what devices you are trying to use. This system has Windows 10 Professional installed, so it has native NVMe drivers available from Microsoft.

I did some quick and dirty I/O testing today with CrystalDiskMark 5.02. The two NVMe devices are both using the native Microsoft NVMe drivers from Windows 10. As you can see below, both the Samsung 950 PRO and the Intel 750 PCIe NVMe cards have tremendous sequential and random I/O performance!

 

Device Sequential Reads Sequential Writes Random Reads Random Writes
512GB Samsung 950 Pro 2595 MB/s 1526 MB/s 171755.6 IOPS 104801.3 IOPS
400GB Intel 750 2369 MB/s 1081 MB/s 177938.0 IOPS 151642.1 IOPS
512GB Samsung 850 Pro 1104 MB/s 532 MB/s 100420.4 IOPS 60765.1 IOPS
6TB WD Red HD 176 MB/s 170 MB/s 386.7 IOPS 448.2 IOPS

Table 1: Sequential and Random Results (Queue Depth 32, 1 Thread)

Keep in mind that the two Samsung 850 PRO SSDs are using hardware RAID1, which seems to help their sequential read performance, and that the two NVMe devices are both using the native Microsoft NVMe drivers, which may be hurting their performance somewhat.

 

image

Figure 1: 512GB Samsung 950 Pro M.2 PCIe NVMe Results

 

image

Figure 2: 400GB Intel 750 PCIe NVMe Results

 

image

Figure 3: 512GB Samsung 850 Pro SATA 3 (RAID 1) Results

 

image

Figure 4: 6TB Western Digital Red Results

SQL Server Diagnostic Information Queries for October 2015

This month, I spent some time adding columns for the new SERVERPROPERTY options, along with adding more comments and links to the scripts. The SQL Server 2016 version will continue to be improved with more SQL Server 2016-specific queries and new columns in existing queries over the next few months as I discover interesting new things in SQL Server 2016. I am also continuing to add more relevant comments and links to the other active versions of these queries in order to help better interpret the results of these queries and save me time in looking up supporting documentation.

Rather than having a separate blog post for each version, I have just put the links for all six major versions in this single post. There are two separate links for each version. The first one on the top left is the actual diagnostic query script, and the one below on the right is the matching blank results spreadsheet, with labeled tabs that correspond to each query in the set. 

Here are links to the latest versions of these queries for SQL Server 2016, 2014 and 2012:

SQL Server 2016 Diagnostic Information Queries (October 2015)

SQL Server 2016 Blank Results

SQL Server 2014 Diagnostic Information Queries (October 2015)

SQL Server 2014 Blank Results

SQL Server 2012 Diagnostic Information Queries (October 2015)

SQL Server 2012 Blank Results

Here are links to the most recent versions of these scripts for SQL Server 2008 R2 and older:

Since SQL Server 2008 R2 and older are out of Mainstream support from Microsoft (and because fewer of my customers are using these old versions of SQL Server), I am not going to be updating the scripts for these older versions of SQL Server every single month going forward.  I started this policy seven months ago, and so far, I have not heard any complaints.

SQL Server 2008 R2 Diagnostic Information Queries

SQL Server 2008 R2 Blank Results

SQL Server 2008 Diagnostic Information Queries

SQL Server 2008 Blank Results

SQL Server 2005 Diagnostic Information Queries

SQL Server 2005 Blank Results

The basic instructions for using these queries is that you should run each query in the set, one at a time (after reading the directions for that query). It is not really a good idea to simply run the entire batch in one shot, especially the first time you run these queries on a particular server, since some of these queries can take some time to run, depending on your workload and hardware. I also think it is very helpful to run each query, look at the results (and my comments on how to interpret the results) and think about the emerging picture of what is happening on your server as you go through the complete set. I have some comments in the script on how to interpret the results after each query.

You need to click on the top left square of the results grid in SQL Server Management Studio (SSMS) to select all of the results, and then right-click and select “Copy with Headers” to copy all of the results, including the column headers to the Windows clipboard. Then you paste the results into the matching tab in the blank results spreadsheet.

About half of the queries are instance specific and about half are database specific, so you will want to make sure you are connected to a database that you are concerned about instead of the master system database. Running the database-specific queries while being connected to the master database is a very common mistake that I see people making when they run these queries.

Note: These queries are stored on Dropbox. I occasionally get reports that the links to the queries and blank results spreadsheets do not work, which is most likely because Dropbox is blocked wherever people are trying to connect.

I also occasionally get reports that some of the queries simply don’t work. This usually turns out to be an issue where people have some of their user databases in 80 compatibility mode, which breaks many DMV queries, or that someone is running an incorrect version of the script for their version of SQL Server.

It is very important that you are running the correct version of the script that matches the major version of SQL Server that you are running. There is an initial query in each script that tries to confirm that you are using the correct version of the script for your version of SQL Server. If you are not using the correct version of these queries for your version of SQL Server, some of the queries are not going to work correctly.

If you want to understand how to better run and interpret these queries, you should consider listening to my three latest Pluralsight courses, which are SQL Server 2014 DMV Diagnostic Queries – Part 1SQL Server 2014 DMV Diagnostic Queries – Part 2 and SQL Server 2014 DMV Diagnostic Queries – Part 3. All three of these courses are pretty short and to the point, at 67, 77, and 68 minutes respectively. Listening to these three courses is really the best way to thank me for maintaining and improving these scripts…

Finally, if you want to get even more information about how to run and interpret these queries, you should consider attending my half-day session Dr. DMV’s Troubleshooting Toolkit at the PASS Summit 2015 starting at 9:30AM on Friday, Oct 30, 2015 in Seattle.

Please let me know what you think of these queries, and whether you have any suggestions for improvements. Thanks!

SQL Server 2014 SP1 Cumulative Update 3 Released

On October 19, 2015, Microsoft released SQL Server 2014 Service Pack 1 Cumulative Update 3 (Build 12.0.4425.19). This CU has 36 updates in the public fix list. If you are on the Service Pack 1 branch of SQL Server 2014 (which is where you should be by now, in my opinion), then you should be planning how you will test and deploy this cumulative update on your database servers in a timely fashion.

If you are still on the RTM branch of SQL Server 2014, Microsoft has also released SQL Server 2014 RTM Cumulative Update 10 (Build 12.0.2556.4), which has 30 updates in the public fix list.

The official Microsoft SQL Server 2014 Build versions list is here, while the SQLSentry SQL Server 2014 Build List is here.

I also have a link page, that points to updated posts about the more interesting hotfixes in cumulative updates for the various active SQL Server versions and branches called SQL Server Cumulative Update Highlights.

Finally, for the CU-skeptics out there, I have noticed this verbiage from Microsoft is now included with the Knowledge Base article’s for individual hotfixes:

Recommendation: Install the latest cumulative update for SQL Server

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. We recommend that you download and install the latest cumulative updates for SQL Server:

Building a Z170 Desktop System with a Core i7-6700K Skylake Processor

Back when I started at SQLskills in May of 2012, I built myself a pretty nice Z77 chipset system with an Intel Core i7-3770K Ivy Bridge processor and 32GB of RAM, running Windows 7 Enterprise Edition. This system uses an ASUS P8Z77-V Deluxe motherboard, with one 512GB OCZ Vertex 4 SSD. It was about the fastest mainstream system that I could build 3.5 years ago. It is mildly overclocked, to 4.3GHz, and it has been extremely reliable over the years as I have used it for much of my daily work.

Some basic information about this system is shown in Figures 1, 2 and 3 below:

image

Figure 1: CPU-Z CPU Tab for Z77 Core i7-3770K System

 

image

Figure 2: CPU-Z Bench Tab for Z77 Core i7-3770K System

 

image

Figure 3: Geekbench 3.3.2 Scores for Z77 Core i7-3770K System

 

Even though this system is still pretty fast, I felt like I could do better in some areas, with a current generation Z170 chipset system with an Intel Core i7-6700K Skylake processor and 64GB of RAM. Last Saturday, I built this new system, and got Windows 10 Professional installed.

Here is the parts list for this system:

  1. Fractal Design Define R5 case
  2. Seasonic SS-660XP2 power supply
  3. ASRock Z170 Extreme 7+ motherboard (Micro Center’s web page has it mislabeled as an Extreme 7)
  4. Intel Core i7-6700K processor
  5. Scythe Kotetsu CPU cooler
  6. (2) 32GB Corsair Vengeance LPX 2666MHz DDR4 RAM kits
  7. (2) 512 GB Samsung 850 Pro SATA III SSDs in hardware RAID 1
  8. 400GB Intel 750 PCIe NVMe storage card

Initially, I’ll be using the Intel integrated graphics, but I may end up using an EVGA Geforce GTX 960 video card. But then again, I may not, since I want to reduce my power usage and have more PCIe lanes available for storage use.

I spent a couple of hours putting this system together, doing a pretty careful job with the cable management. When I had it ready to turn on for the first time (without putting the case sides on, which is always bad luck), I was rewarded with the CPU and case fans spinning, but no visible POST or video output at all. Luckily, the ASRock motherboard has a built-in LED diagnostic display, which was showing a code 55 error. Looking this up in the motherboard manual, I discovered that this was a memory-related issue. I removed two of the 16GB DDR4 RAM modules, and powered it back up, and this time I got a POST.

Going into the UEFI BIOS setup, I discovered that my ASRock Z170 Extreme 7+ motherboard had the initial 1.4 BIOS, while the latest version was 1.7. One of the fixes listed for version 1.7 is “improve DRAM compatibility”. I was able to flash the BIOS to 1.7 using the Instant Flash utility in the UEFI BIOS setup, and then I was able to use all four 16GB DDR4 RAM modules.

Next I created a RAID 1 array with my two 512GB Samsung 850 Pro SSDs, using the Intel RAID controller that is built-in to the Z170 chipset. I made sure the Intel 750 was not installed yet, and then I used an old USB optical drive to install Windows 10 Professional on to the RAID 1 array. Windows 10 Professional installed default drivers for the dual Intel 1GB NICs, so I was able to get on the internet and download and install all of the latest Windows 10 64-bit drivers for this motherboard from the ASRock web site. Then I used Windows and Microsoft Update to get Windows 10 fully patched.

Windows 10 recognized the Intel 750 using the default Microsoft NVMe drivers. I will benchmark using those drivers, and then compare the results to the native Intel NVMe drivers. So far, I have benchmarked the new system using CPU-Z and Geekbench 3.3.2. The basic information and scores for the new system is shown in Figures 4. 5, and 6 below:

clip_image002

Figure 4: CPU-Z CPU Tab for Z170 Core i7-6700K System

 

clip_image002[5]

Figure 5: CPU-Z Bench Tab for Z170 Core i7-6700K System

 

clip_image002[7]

Figure 6: Geekbench 3.3.2 Scores for Z170 Core i7-6700K System

 

Keep in mind, that beyond enabling XMP 2.1, I have not overclocked the new system yet. The new system is about 10-20% faster than the old system, from a CPU and memory perspective, depending on which benchmark you choose. In some respects, this is disappointing, but the real advantage of the new system is having twice the RAM, and a lot more potential I/O bandwidth with the Z170 Express chipset. With Windows 10 Professional, I have Hyper-V support (and the Core i7-6700K supports VT-x and VT-d), so I can run more VMs simultaneously. I also have two Intel 1GB NICS, which I plan to use together with NIC teaming in Windows 10.

I plan on getting at least one of the upcoming 512GB Samsung 950 Pro M.2 NVMe cards (and this motherboard has three Ultra M.2 slots) when they are released in October/November, so I will have plenty of disk space and I/O performance for the VMs.

System CPU-Z Single Thread CPU-Z Multi-Thread Geekbench Single-Core
Core i7-3770K 1573 5920 3680
Core i7-6700K 1711 6815 4404

Building a Desktop Workstation for SQL Server Development and Testing

Back in March of 2014, I wrote a fairly long blog post called Building a Workstation for SQL Server 2014 Development and Testing, which still generates quite a bit of hits and e-mail. Since it is about eighteen months later, I thought it was about time to update this information to cover the latest available hardware choices.

With the current selection of high-performance and very affordable desktop computer components, it is not very difficult to assemble an extremely high performance workstation for SQL Server development and testing at a very reasonable cost. Depending on how much performance you want and what your available budget is, you can take several different routes to get this accomplished.

At the high end of the spectrum, you can get a Socket 2011 v3 motherboard, with an Intel Xeon E5-2600 v3 product family “Haswell-EP” processor or an Intel Core i7-5800 product family “Haswell-E” processor and up to 64GB or 128GB of ECC DDR4 RAM, and multiple PCIe flash storage cards, and spend a pretty significant amount of money, depending on your exact hardware and storage choices. 

In the middle, you can build a very powerful system using the new 14nm Intel Core i7-6700K “Skylake” processor that uses a new LGA 1151 motherboard and DDR4 memory. Skylake processors require a newer Intel chipset, and the first Skylake motherboards that are available are using the high-end Z170 Express chipset. Aside from DDR4 support, the most interesting improvement to Z170 Express is an increased number of PCIe lanes. The Z170 chipset supports a total of 20 PCI-Express lanes at the PCH in conjunction with the CPU’s 16 PCIe 3.0 lanes for a platform total of 36. Last generation’s Z97 Express chipset coupled with Devil’s Canyon or Haswell CPUs only allowed for 24 PCIe 2.0 lanes. All of these from the PCH were only PCIe 2.0 compliant. In contrast, all of the Z170’s PCIe lanes are Generation 3.0 compliant while retaining backwards compatibility with PCIe 2.0 and 1.0 specifications. This means you have a lot more I/O bandwidth available for storage.

At the lower end of the spectrum, you can put together a system with a single Intel Core i7-4790K “Devil’s Canyon” processor, 32GB of non-ECC DDR3 RAM, and a single high-performance, 6Gbps consumer-class SSD, and still have a system with more processing power than many existing Production database servers. A system that uses this older generation architecture will still be quite powerful, but will be more economical than ever, since the Skylake family has been released.

If you are going to build a desktop system from scratch, you need eight basic components:

  1. Computer Case
  2. Power Supply
  3. Motherboard
  4. Processor
  5. Memory (RAM)
  6. Storage (magnetic or flash)
  7. Discrete Video Card (optional, not really necessary in most cases)
  8. Optical Drive (optional, becoming much less important)

This assumes that you have a keyboard, mouse, and one or more monitors. I’ll discuss each one of these components, with some tips for what you should consider as you are choosing them.

Computer Case

You will need some sort of case to hold your components (unless you want to leave them running on a test bench). Personally, I like mid-range, mid-tower cases from companies like Fractal Design, Antec, Cooler Master, and Corsair. Mid-Tower cases give you plenty of room for common ATX motherboards, and they usually have at least four to six internal 3.5” or 2.5” drive bays. Newer designs have special 2.5” mounting points for SSDs and front or top mounted USB 3.0 or USB 3.1 ports. Better cases are much easier to work with, and they often have much better cable management features (so you can route most of your cables in a separate space under the motherboard). This not only looks much nicer, but it gives you better airflow inside the case. You probably don’t really need a fancy, gaming-oriented case with LED lighting and a huge number of case fans. A decent case in the $50-100 range will usually have good quality components (such as quieter, larger diameter case fans), along with good thermal and noise management features. The Fractal Design Core 3300 is a good example of an affordable, good quality case for about $80.00. You can spend a little less on a case, or quite a bit more. Just make sure that the case will allow you to install the size of motherboard that you will be using.

Power Supply

You should invest in a decent quality power supply as opposed to the cheapest one you can find. You don’t want to go overboard and get a 1200 watt behemoth gaming-oriented power supply (unless you are building an extreme gaming rig with multiple, high-end video cards that really need that much power). For the kind of system that I am recommending, you can use a high quality 400-500 watt 80 PLUS modular power supply and have plenty of reserve power. Modular power supplies have detachable cables for things like SATA power, MOLEX power, PCI-E power, etc., so you only need to plug in and use the cables you actually need.

Power supplies are much less efficient when they are only supplying a very small portion of their rated output. Getting a 1200 watt power supply because you think it must be “better” than a good 500 watt power supply is actually a waste of money, both for the initial cost of your power supply and the electrical power costs over the life of your machine. The components that I am recommending will end up drawing about 30-40 watts at idle.  I really like Seasonic power supplies, especially their fan-less, modular models such as the SS400FL and the newer SS-520FL2. They are both completely silent and highly efficient, 80+ Platinum rated power supplies. Another less expensive alternative that I like are Corsair power supplies, such as the Corsair CX500M modular power supply.

Motherboard

The motherboard is where all of your other components are plugged into, so it is a critical component. You need to consider which processor you are going to be using, since there are several different processor socket types available, which will dictate your motherboard choices. The most common type in late 2015 is the LGA 1150, which will work with the 4th generation, 22nm Intel Core processors (Haswell and Devil’s Canyon). You also need to consider the form-factor of your motherboard. You can choose from ATX, micro-ATX, and mini-ITX, which refers to the size of the motherboard. You also need to think about the chipset used on your motherboard.

The Intel Z97 Express chipset is their best chipset for an LGA 1150 motherboard. As you are looking at motherboards, you should be looking at the low-to-mid range Z97-based motherboards instead of the high-end, gaming motherboards. The high-end gaming Z97 motherboards can be quite expensive, and they will probably have features (such as support for three discrete video cards), that you don’t really need for a SQL Server workstation or test server. Instead, make sure you choose a model that has four DDR3 RAM slots, and at least six 6Gbps SATA ports. You also might want a model that has one or more M.2 slots. A good example Z97 motherboard is the ASRock Z97 Extreme6/3.1.

A newer, slightly more expensive choice is a 6th generation, 14nm Intel Core processor (Skylake), combined with a Z170 chipset. Right now, there are only two Skylake processor choices that are widely available, the Core i7-6700K, and the Core i5-6600K. Skylake processors use the the new Socket LGA 1151, and DDR4 RAM, so you will need a new motherboard and new memory if you are upgrading from an older platform. Unlike older Intel processors, these new Skylake processors do not come with a stock cooling fan bundled with the processor, so you will have to buy some type of CPU cooler. A good example Z170 motherboard is the ASRock Z170 Extreme7 +. The reason I really like this motherboard is because of all of the I/O capacity and flexibility that it offers, with three PCIe 3.1 x16 slots, and three Ultra M.2 PCIe 3 x4 slots.

If you are going to run Windows Server 2012 R2 for your host operating system, you should be aware that most Intel embedded NICs that you will find on many desktop motherboards will refuse let you install the NIC drivers with a Microsoft server operating system. In that case, you can buy an inexpensive, non-Intel ($15-20) PCI-E Gigabit Ethernet card that work just fine. If you are running Windows 8.1 or Windows 10 for your host operating system, you won’t have this issue.

Processor

You can choose a modern, Intel desktop processor that may well have much more raw processing power than many older two or four-socket production database servers. This is not an exaggeration, although it depends on the age of your production database server. You are far more likely to run into memory or I/O bottlenecks as you push a modern Intel desktop system than processor bottlenecks. For most people, an Intel Core i7-4790K processor will be your best choice (especially if you live near a Micro Center). It is a quad-core processor with hyper-threading (so you have eight logical cores) that runs at a base clock speed of 4.0GHz, with the ability to TurboBoost to 4.4GHz. It runs very cool, and is easy to overclock even with the stock Intel processor cooler. It is not really necessary to overclock this processor, to get good performance. You can have a maximum of 32GB of DDR3 RAM with this processor, and it supports both VT-x and VT-d for better virtualization performance.

Most 4th generation Intel Core processors (Haswell) have pretty good integrated graphics built-in to the CPU package. The better models have HD4600 graphics which give you more than enough performance for normal desktop usage and even some moderate gaming. There was a pretty big improvement in the integrated graphics performance between the Ivy Bridge and Haswell processors, so it is much more feasible to simply use the integrated graphics instead of buying a separate, discrete video card. This will save you money and reduce your electrical power usage.

One big variable in the cost of using this processor is whether you live near a Micro Center computer store or not. Micro Center has 25 locations in the Continental United States, and they sell a few specific models of Intel processors at prices that no other company seems willing to match. They have been doing this for years, and it is their regular practice (so it is not a special sale or promotion). The only catch is that those processors are only available for in-store pickup (so no mail-order).

For example, Micro Center is currently selling the Intel Core i7-4790K processor for $279.99, while NewEgg is selling the exact same Intel Core i7-4790K processor for $339.99. Micro Center quite often does promotions where they will reduce the price of a motherboard by $40-$50 if you buy the motherboard with a qualifying processor. Their prices on motherboards, cases, memory, hard drives and SSDs are also quite competitive.

A newer Intel Core i7-6700K processor will cost $349.99 at Micro Center, and it will cost $369.99 at NewEgg.

Memory

If you select an LGA 1150, Z97 Express motherboard with four RAM slots, you can have up to 32GB of non-ECC DDR3 RAM in your system. You can get two 8GB sticks of 240-pin PC3 12800 DDR3 RAM for about $89.00, so it would be about $178.00 to get 32GB of RAM. This should be plenty for most development and testing workloads (including running multiple VMs), but if you really need more, you could make the jump to the LGA 2011 v3 platform that uses the more expensive six and eight-core Intel Haswell-E processors where you can eventually have up to 128GB of DDR4 RAM.

DDR4 RAM is a little bit more expensive than DDR3 RAM, but the price differential is not really that large. For example, you can get two 8GB sticks of 288-pin PC4 17000 DDR4 RAM for about $105.00, so it would be about $210.00 to get 32GB of RAM. Eventually, you will be able to get 16GB DDR4 DIMMs, so you will be able to have 64GB of RAM in a Z170 Express system.

One thing you will want to do as you are configuring your system is to go into your BIOS setup and turn on Extreme Memory Profile (XMP), so that you will get better memory performance. This can occasionally cause stability problems, depending on the type of memory that you have, but if that happens, you can always turn it back off.

Storage

You will need some type of storage for your system. Traditional magnetic hard drive prices continue to decline, so that you can get a high-performance 3TB, 7200rpm SATA III drive with 64MB of cache, such as a 3TB Western Digital WD Black WD3003FZEX for $149.99. For just a little more money, you can also get a much smaller, but much much higher performance 6Gbps SATA III consumer-grade SSD, such as a 500GB Samsung 850 EVO SSD for $179.99. Solid State Drive prices have come down a lot (as performance has increased dramatically) over the past couple of years, but they still cost about six times as much as conventional magnetic storage, per gigabyte.

I really encourage you to use a modern, fast 6Gbps SATA III SSD for your boot drive since it will have an extremely dramatic, positive effect on how fast your system performs and “feels” in everyday use. It will boot faster, shut down faster, programs will load nearly instantly, and it will take much less time to install new software and Windows Updates. It is similar to the difference between a dial-up modem and a fast broadband connection. Once you start using a fast SSD, you will never want to go back to a conventional magnetic hard drive.

You want to make sure your fast 6Gbps SSD is plugged into a 6Gbps SATA III port (not one of the 3Gbps SATA II ports). Otherwise, your fast SSD will be limited to about 275MB/sec for sequential reads and writes (which is still about twice as fast as a very fast traditional 7200rpm SATA hard drive). You also want to avoid the smallest capacity 64GB and 128GB SSD models, since their performance is much usually much lower than the larger capacity models from the same manufacturer and product line. This is because the smaller capacity models have fewer NAND chips and fewer data channels. Ideally, you would want a 250GB (or larger) 6Gbps SATA III SSD plugged into each SATA III port that you have available on your motherboard. This would give you lots of options for how to lay out your SQL Server data files, log files, tempdb files and SQL Server backup files.

Of course, you may not want to spend that much money, so it is still common to have one or two SSDs, along with one or more conventional magnetic drives in a desktop system. One of the luxuries with a desktop system compared to any laptop is that you have a very high number of internal drive bays and up to ten or twelve SATA III ports on the motherboard. You can also buy inexpensive PCI-E SATA III cards to add even more SATA III ports to a desktop system.

If you want even more storage performance, you may want to consider a PCIe NVMe flash storage card such as the Intel 750 Series, which comes in 400GB, 800GB, and 1.2TB capacities. These cost slightly less than $1.00/GB, and their performance is about 4-5 times better than SATA III SSDs for reads and about 2-3 times better for writes. Another alternative that will be available in October is the new Samsung 950 Pro Series of M.2 PCIe NMVe flash devices, which will initially come in 256GB and 512GB capacities. If you have one or more M.2 slots that support PCIe 3.0 x4, then you will also get tremendous performance from these.

Discrete Video Card

There are some situations where the Intel integrated graphics might not be enough for your needs. An example would be if you were doing things such as AutoCad that really place a lot of stress on your graphics performance. Another example is if you wanted to run multiple, large monitors on your system. Most motherboards that support the Intel integrated graphics only have two or three video connectors (such as a VGA connector, DVI connector and an HDMI connector), so that would limit how many monitors you could connect to the system. Depending on your processor choice, you may not have integrated graphics at all.

If you do decide to go with one or more discrete video cards, you can get quite decent performance for about $100-150.00 each (but you can spend much, much more). You may also need a power supply with multiple, supplemental PCI-E power connectors, and you might even need a higher capacity power supply.

Optical Drive

Even though they are becoming much less useful over time, it can still be useful to have a DVD-Recorder, optical drive in a desktop system. It just makes it easier to install the operating system and other software (although you can certainly install from a USB drive). It is also becoming much more common to simply mount an .iso file for doing something like installing SQL Server 2014. You can get bare, OEM optical DVD drives for about $15-20. Personally, I like to use an external USB optical drive to install the operating system, so I don’t have to have an internal optical drive taking up space and power in the system.

So, after all of this, how much money am I trying to convince you to spend?  Well, here is one example:

  1. Case                   $80.00
  2. Power Supply       $50.00
  3. Motherboard      $190.00          (ASRock Z97 Extreme 6 USB 3.1 from Micro Center)
  4. Processor          $270.00          (Intel Core i7-4790K from Micro Center)
  5. RAM                  $178.00          (32GB of DDR3 RAM)
  6. Storage             $330.00          (One 500GB Samsung 850 EVO SSD and one 3TB 7200rpm drive)
  7. Optical drive         $20.00

Total System         $1118.00

This system would have much better performance than a laptop that would cost several times as much. It would also have better performance than many production SQL Server database servers. It would be pretty easy to slice over $400.00-$500.00 off of this system cost by choosing some different components, and still have a very capable system.

Of course, a desktop system like this does not have redundant, server-class components or ECC RAM, so you would not want to use them in a production situation. They would probably be much better (in terms of performance) than some ancient, out of warranty, retired server for development and testing.

SQL Server Diagnostic Information Queries for September 2015

This month, I spent quite a bit of time synchronizing the scripts between the SQL Server 2016, 2014, and 2012 versions, making sure the small differences that were cropping up between the versions were cleaned up as much as possible. The SQL Server 2016 version will continue to be improved with more SQL Server 2016-specific queries and new columns in existing queries over the next few months as I discover interesting new things in SQL Server 2016. I am also continuing to add more relevant comments and links to the other active versions of these queries in order to help better interpret the results of these queries and save me time in looking up supporting documentation.

Rather than having a separate blog post for each version, I have just put the links for all six major versions in this single post. There are two separate links for each version. The first one on the top left is the actual diagnostic query script, and the one below on the right is the matching blank results spreadsheet, with labeled tabs that correspond to each query in the set. 

Here are links to the latest versions of these queries for SQL Server 2016, 2014 and 2012:

SQL Server 2016 Diagnostic Information Queries (September 2015)

SQL Server 2016 Blank Results

SQL Server 2014 Diagnostic Information Queries (September 2015)

SQL Server 2014 Blank Results

SQL Server 2012 Diagnostic Information Queries (September 2015)

SQL Server 2012 Blank Results

Here are links to the most recent versions of these scripts for SQL Server 2008 R2 and older:

Since SQL Server 2008 R2 and older are out of Mainstream support from Microsoft (and because fewer of my customers are using these old versions of SQL Server), I am not going to be updating the scripts for these older versions of SQL Server every single month going forward.  I started this policy six months ago, and so far, I have not heard any complaints.

SQL Server 2008 R2 Diagnostic Information Queries

SQL Server 2008 R2 Blank Results

SQL Server 2008 Diagnostic Information Queries

SQL Server 2008 Blank Results

SQL Server 2005 Diagnostic Information Queries

SQL Server 2005 Blank Results

The basic instructions for using these queries is that you should run each query in the set, one at a time (after reading the directions for that query). It is not really a good idea to simply run the entire batch in one shot, especially the first time you run these queries on a particular server, since some of these queries can take some time to run, depending on your workload and hardware. I also think it is very helpful to run each query, look at the results (and my comments on how to interpret the results) and think about the emerging picture of what is happening on your server as you go through the complete set. I have some comments in the script on how to interpret the results after each query.

You need to click on the top left square of the results grid in SQL Server Management Studio (SSMS) to select all of the results, and then right-click and select “Copy with Headers” to copy all of the results, including the column headers to the Windows clipboard. Then you paste the results into the matching tab in the blank results spreadsheet.

About half of the queries are instance specific and about half are database specific, so you will want to make sure you are connected to a database that you are concerned about instead of the master system database. Running the database-specific queries while being connected to the master database is a very common mistake that I see people making when they run these queries.

Note: These queries are stored on Dropbox. I occasionally get reports that the links to the queries and blank results spreadsheets do not work, which is most likely because Dropbox is blocked wherever people are trying to connect.

I also occasionally get reports that some of the queries simply don’t work. This usually turns out to be an issue where people have some of their user databases in 80 compatibility mode, which breaks many DMV queries, or that someone is running an incorrect version of the script for their version of SQL Server.

It is very important that you are running the correct version of the script that matches the major version of SQL Server that you are running. There is an initial query in each script that tries to confirm that you are using the correct version of the script for your version of SQL Server. If you are not using the correct version of these queries for your version of SQL Server, some of the queries are not going to work correctly.

If you want to understand how to better run and interpret these queries, you should consider listening to my three latest Pluralsight courses, which are SQL Server 2014 DMV Diagnostic Queries – Part 1SQL Server 2014 DMV Diagnostic Queries – Part 2 and SQL Server 2014 DMV Diagnostic Queries – Part 3. All three of these courses are pretty short and to the point, at 67, 77, and 68 minutes respectively. Listening to these three courses is really the best way to thank me for maintaining and improving these scripts…

Finally, if you want to get even more information about how to run and interpret these queries, you should consider attending my half-day session Dr. DMV’s Troubleshooting Toolkit at the PASS Summit 2015 starting at 9:30AM on Friday, Oct 30, 2015 in Seattle.

Please let me know what you think of these queries, and whether you have any suggestions for improvements. Thanks!

Samsung 950 PRO M.2 PCIe NVMe SSD

Samsung has announced their new 950 PRO M.2 PCIe NVMe solid state drive, which is potentially great news if you are considering building a new system (or have a new enough system that has M.2 slots that support PCIe 3.0 x4 speeds)

According to the press release:

The 950 PRO will be available in 512 gigabyte (GB) and 256GB storage capacities. The 512GB version delivers sequential read/write speeds of up to 2,500 MB/s and 1,500 MB/s. Random read performance is up to 300,000 IOPS, with write speeds of up to 110,000 IOPS.

Both capacities come with a 5-year limited warranty up to 200 terabytes written (TBW) for the 256GB and 400TBW for the 512GB. The 950 PRO will be available beginning in October 2015, with an MSRP of $199.99 for the 256GB capacity and $349.99 for the 512GB capacity.

TheSSDReview has a good story about this drive here.

In case you are wondering, NVMe or NVM Express (Non-Volatile Memory Express) is an optimized, high performance, scalable host controller interface with a streamlined register interface and command set designed for enterprise and client systems that use PCIe SSDs. It typically offers much better performance than the legacy AHCI (Advanced Host Controller Interface) interface used by some PCIe solid state drives (and all SATA solid state drives). You can read more about NVM Express here.

I am getting close to buying the parts for a new Z170-based, Core i7-6700K desktop system to replace my current Z77-based Core i7-3770K system that I built in early 2012. I am going to be using an ASRock Z170 Extreme7+ motherboard for this new system, mainly because all of the I/O capacity that it offers, including four PCIe 3.1 x16 slots, and three “Ultra” M.2 PCIe 3.0 x4 slots. It also has ten SATA 3 ports, three SATA Express ports, and USB 3.1 Type A and C support.

Even with the new Z170 chipset, you won’t be able to use all of this I/O capacity, since you only have 26 high-speed I/O lanes available, but you should be able to put three Samsung 950 PRO M.2 drives into the three available slots on this motherboard.

 

 

Figure 1: ASRock Z170 Extreme7+ Motherboard

If you want to be able to use one of these very fast M.2 solid state drives, you will need to make sure that your system has an M.2 slot that is also long enough (80mm) to accommodate the card. You will also want your M.2 slot to support PCIe 3.0 x4 (meaning four lanes), which is sometimes called “Ultra M.2”.

SQL Server 2012 SP2 Cumulative Update 8 Available

Microsoft has released SQL Server 2012 Service Pack 2 Cumulative Update 8, which is Build 11.0.5634.1. This CU has 23 fixes in the public fix list, and a number of them look pretty significant. If you are on SQL Server 2012, you need to be on the Service Pack 2 branch by now (especially since the RTM and SP1 branches are no longer “supported service packs”). If you are on SP2, I think you are much better off on the latest cumulative update than on the original SP2 RTM build.

Analyzing and Improving I/O Subsystem Performance Precon in Denver

On September 18, 2015, I will be presenting Analyzing and Improving I/O Subsystem Performance as an all day pre-conference session the day before SQLSaturday #441 in Denver. This session should be a lot of fun and will be very useful for SQL Server database administrators and other I.T. professionals who work with SQL Server. Here is the abstract:

SQL Server is often I/O bound, but proving it to your storage or SAN administrator can be challenging! You will learn about the different types of storage that are available for SQL Server, and how to decide what type of storage to use for different SQL Server workload and file types. You will also learn useful tips and techniques for configuring your storage for the best performance and reliability for your workload. There will be extensive coverage on how to use disk benchmark tools like CrystalDiskMark 4.0, SQLIO and Microsoft DiskSpd, so you can confidently understand the performance that your I/O subsystem can deliver. We’ll also cover methods to effectively measure and monitor your storage performance from an OS and SQL Server perspective so that you will have valuable information and evidence available the next time you have to discuss I/O performance with your storage administrator. You will also learn a number of valuable OS and SQL Server configuration settings that will help you get the best I/O performance possible from your storage subsystem.

I hope to see you there and at SQLSaturday #441 the next day!

SQL Server 2014 SP1 Cumulative Update 2

On August 17, 2015, Microsoft released SQL Server 2014 SP1 Cumulative Update 2, which is Build 12.0.4422. This CU has 44 hotfixes in the public fix list, which is a relatively high number. This shows that Microsoft has been busy fixing important SQL Server issues, and it also underscores the importance of paying attention to cumulative updates and making an effort to stay current with your builds of SQL Server.

They also released SQL Server 2014 RTM CU9, which is Build 12.0.2553. This CU has 30 hotfixes in the public fix list. Personally, I think you should be moving to the SQL Server 2014 SP1 branch by now, or in the very near future, rather than staying on the RTM branch much longer.