TIA,
Ian
Well you do not want to hear that answer, but it depends.It′s like asking, How much gas will I need when I travel from NYC to Seattle. Well that depends on how much data / luggage will be transported, which transport device you use, how much data will be retrieved, how often you will query the database, how many users will access the database, etc. There are many parameters to consider.
Jens K. Suessmeyer.
http://www.sqlserver2005.de
sql
- 2 tables, approximately 100.000 records, the tables joined in 1:1 relation, one record is approximately 500 bytes long
- typical scenario:
- select what returns 1 or zero record
- if it returned 1 record an update performed on this record
- the event logged in a third table (one insert)
- this typical scenario needs to run 100-300 times in every second
Can you tell me any advice on sizing of hardware for this? We can rely on a well designed database structure (proper indexes, etc...)
Thanx in advance
It is really a smallish database.
These are just minimal suggestions, and without more detail, they are just as good as visiting a seer.
A dual proc, dual core box, 64 bit
4GB memory -8GB would be better
64 Bit Win2003 Server
64 bit SQL Server
A SAN/NAS (or drive array) with the following LUNs/Drives: (I would go for 15K, 144GB or larger, drives.
Drive/LUN for TempDB
Drive/LUN for Log file
Drive/LUN for Database
(Separate local drive for OS and virtual memory file.)
By combining 64bit software with the fastest possible hardware you can afford, you will have planned ahead for scaling out.
