As we discussed in our last column “Why Is Storage Hardware Sprawl Worse Than Ever?”, toward the end of the last decade (2007-2010) the data center began to tap into the abundance of compute power available to it but providing…
As we discussed in our last column “Why Is Storage Hardware Sprawl Worse Than Ever?”, toward the end of the last decade (2007-2010) the data center began to tap into the abundance of compute power available to it but providing…
In our webinar, “Overcoming the RoadBlocks to the All-Flash Data Center”, one of the questions that came up is how to integrate an All-Flash Array into the data center. It’s not our position that you should throw out all your…
SQL Databases of almost any size should be a top consideration for SSD integration. Because of the granularity of the database structure small components of the database can be moved to SSD, reducing the overall SSD investment. In this article, Storage Switzerland’s Lead Analyst, George Crump discusses how to determine which of those componets should be on SSD. This report will show that a surprisingly small amount of SSD can provide a cost effective, more scaleable, higher performing database for the entire environment.
Learn:
Which Storage Statistics Can Help You Determine SQL SSD Readiness
Which component of your SQL environment should be on SSD
The ROI of SSD Investment for SQL Environments
IT professionals wear many hats and are constantly responding to the emergency of the moment. When performance problems appear in the virtual environment the default reaction is to throw hardware at the problem. That means “throwing” premium priced flash SSD at it. But this approach can lead to buying too much or too little SSD, which either wastes money or doesn’t effectively solve the performance problem. In this article Storage Switzerland’s lead analyst George Crump, leads you through the process of qualifying your virtual environment’s SSD suitability.