• 11

A PHP Error was encountered

Severity: Notice

Message: Undefined index: userid

Filename: views/question.php

Line Number: 191


File: /home/prodcxja/public_html/questions/application/views/question.php
Line: 191
Function: _error_handler

File: /home/prodcxja/public_html/questions/application/controllers/Questions.php
Line: 433
Function: view

File: /home/prodcxja/public_html/questions/index.php
Line: 315
Function: require_once

I have a Microsoft SQL Server 2008 database which contains approximately 3 GB of data. The server has 4 GB of RAM. The database is used both for reading and for writing data (lots of changes). The server is rebooted very rarely.

I want to improve the read-write performance. Will a replacement of an actual HDD (no RAID) by a solid state drive improve performance?

Since over time, SQL Server is known to fill all the remaining RAM, I suppose that if I extend actual RAM to 8 GB, it will be enough to "cache" in RAM all the data used by the SQL Server. So, in my case, there is absolutely no need to buy a solid state drive, or, at least, the performance gain will be quite small. Is that right?

Mostly depends on if your current storage uses a battery-backed-write-cache raid card. If so, it probably won't make much if a difference considering how much of your dataset fits in memory. It will probably help nightly-report type queries more than more transactional application queries.

  • 3
Reply Report

When you run the SQL Profiler tool are you showing obvious file I/O performance problems? Have you used the profiler to identify where your bottleneck actually is?

  • 1
Reply Report
      • 1
    • +1. No, I haven't profiled the whole thing (only single queries during development a year ago), and yes, it's a good idea to start by identifying the bottleneck. In fact, the machine has a quite powerful CPU, so even if some queries are poorly written, it's ok most of the time. Moreover, the actual hdd seems to be solicited intensively, as shown by Resource Monitor.

Trending Tags