Posted by Rich on 10/01/24 11:22

This is what one of the tables looks like - they are all similar and there
are about 60 different tables:

CREATE TABLE SalesData1(
smalldatetime TimeStamp,
varchar(8) CustomerID,
numeric S1,
numeric S2,
numeric S3,
numeric S4,
numeric X
)

I'm not sure on the data types, S1 thru S4 are actually float values with
two decimal places. X is an unsigned long value.

Anyway, the bigger question is what do we need at *minimum* for hard drives
and RAM, if we are using SQL 7.0* under these circumstances:

1. Inserting up to 600,000 records every 10 minutes
2. Updating up to 70,000 records every 10 minutes

We can use BCP for inserting the data. There are many different tables with
an average of 10,000 records being inserted into each one every 10 minutes.

I nearly ordered a couple servers with dual 400GB SATA hard drives using
RAID1, but someone told me that with only 2 drives - it would cause SQL
server to work harder. So do we need a whole bunch of smaller 40GB drives??
Should they be SATA drives?

Could one server with dual Xeon CPUs do this, or do we need more than one
server?
And would 2GB of RAM be sufficient?

All I know is that we will be inserting 600k records, updating 70k records,
and reading 500,000 every 10 minutes.

Do I need to provide more info on anything specifically?

We should have an SQL consultant helping us in the near future - I'm just
trying to get a head start with the hardware. Our budget is small, in fact I
may have to build the servers myself out of spare parts and things on sale
at Fry's :)

Thanks for your help. I will provide more info if needed.

*Can't afford to upgrade to SQL 2000

• Next in forum: Re: Scheduled Job Sometimes Error Sometimes Not
• Prev in forum: Re: MS SQL Reporting Service in Windows 2003 Server
• Thread view: Hardware configuration help for MS SQL server

[Reply to this message]