Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
ready_cents
Starting Member
2 Posts |
 Posted - 2008-11-10 : 15:02:04
|
| Not sure if this is the right forum or if there even is a forum appropriate for this question.My DB is very simple but pretty unusual. I have about 10 tables that are all pretty much the same. They have 1 bigint column which is the primary key. Then they have about 50-200 int columns. Some of the tables have another bigint which leads to a customer table. The application does more writing than it does reading but the reading needs to be done very quickly whereas the writing is not as time critical. The size of my database is currently around 20 gb but it will grow to 100+ gb at some point.Currently I have 8 gb of memory in my computer and 2 hard drives in a raid 0 configuration totalling ~500 gb (more than enough space). What I want is to speed up both reads and writes, but the major emphasis is on reads. For $500 I can do one of the following: -get 8 more gb of memory-get a second RAID controller card and four 7200 RPM drives for a total storage space of around 2 tb. I would then use the first RAID strictly for OS and swapping and the second RAID becomes the DB RAID.More memory means bigger indexes (and therefore faster reads?) which is my argument for more memory. However, more drives means everything is read faster. I am simply not educated enough to determine what will give me more bang for my buck. Any thoughts are appreciated. |
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2008-11-10 : 15:21:48
|
| Before spending any money for hardware, you should looking at optimizing the queries. It might be that all you need is an index to give you the performance you need.CODO ERGO SUM |
 |
|
|
ready_cents
Starting Member
2 Posts |
Posted - 2008-11-10 : 15:25:41
|
| My database is super simple. All queries are done with the only column in the WHERE clause being the primary key. There is only one relationship in the entire schema and it's done via a foreign key.It doesn't matter how fast my schema is (it is very fast), I need it to be faster. |
|
|
|
|
|
|
Scaling up