Box Requirements
From: joe chang (anonymous_at_discussions.microsoft.com)
Date: 03/15/04
- Next message: Branko Kovac: "How to reduce size of sql.log file"
- Previous message: yingjian ma: "IIS is not running"
- In reply to: Bluedolphin: "Box Requirements"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 15 Mar 2004 15:51:05 -0800
i would never recommend raid 5 for database apps unless
there is detailed analysis to show the usual patterns have
very few write queries
try starting with a 4 disk system, 2 RAID 1 partitions,
depending on actual usage, you may be better off having
data and log on separate partitions,
or if log usage is lite, distribute data across both
partitions, log on 1,
if your load grows, thens split data and log
>-----Original Message-----
> Hello All:
>
>I have an Access database that we will be porting to SQL
soon. As a designer and front-end developer, I am weak on
the hardware requirement end. I have always depended on
experienced network / hardware people to to see that my
boxes are up to the task for the system I'm building. In
my current job location, they are not doing a lot of
database work and have outsourced (from what I can tell)
most Database server setup etc., and simply maintain
packaged products. I think this may be their first inhouse
development product. Therefore, I am not sure how much
experience the people I will be meeting with on Wednesday
have in Server requirements either. I would like to gather
some suggestions before my meeting with them on Wednesday.
I want to be sure the box will be able to handle the
system.
>
>Here is the system in a nutshell and what SQL will need
to handle. First of all, this Access system should already
be in SQL in my honest opinion. We are currently just
under one gig in Access and will easily reach the 1.5 gig
point by the end of this school year. Once we start
entering next years data, we will fly past 2 gig probably
within the first month of school, and only grow from
there. The system currently has 50 objects (tables). This
is the base system which handles and stores data for over
115 schools. We will be running some intensive import
routines once a week in the evening and it will eventually
have thousands of online end-users who will be accessing
it daily. Against these base tables, we will build a
reporting database that will aggregate and crunch numbers
into probably 30-40 reporting tables (reporting DB) on a
nightly basis, which will suport hundreds of online
reporting options.
>
>So you can see that I need a robust SQL environment and
my greatest fear is that they will give me a box that is
not up to task. I think I need a minimum of 3 processors
for this type of load and growing DB size (especially with
the HUGE reporting needs that this system requires), but
I'm not sure on hard drive, raid array requirements,
recommended RAM etc. I just was given their basline system
requirements for a server and the specs show the following
server,
>
>Dell 2600 PowerEdge Server
>Processor (2) Dual 2.4GHz
>2GB of memory
>3 36GB (with raid 5) - expandable
>Tape Backup LTO 110/220 GB.
>
>Can anyone tell me if this box will handle it and/or what
upgrades I would need from here? I just need some good
solid third party advise to take to the meeting on
Wednesday. The last thing I need to to go live with a
server that can't handle the load, the background
processing, the desktop AND online users concurrently, the
growth... and we all know how systems grow once they get
started!!
>
>Thanks in advance for any suggestions you can offer!!
>
>.
>
- Next message: Branko Kovac: "How to reduce size of sql.log file"
- Previous message: yingjian ma: "IIS is not running"
- In reply to: Bluedolphin: "Box Requirements"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
