Groups | Blog | Home
all groups > sql server (alternate) > february 2004 >

sql server (alternate) : SQL-2000 with Analysis Services - $ 20k server budget advice


Chuck Conover
2/21/2004 1:38:45 PM
Bruce,
Let me give you benefit of our top client's experience with hardware for
an SQL 2000 server website. Disclaimer: we recommended and set up site 1 in
June of 2001 for the customer, but did not recommend the hardware for site
2; that was done by their internal staff.

Site 1: Total cost $12,000 USD
web server - Dual 800MHz processors, Single 9GB 10K RPM drive, 2GB
RAM - Windows 2000 Server
database/report server - Dual 922MHz processors, 5 Seagate Cheetah
18GB 15K RPM drives in RAID 5, 4GB RAM - Windows 2000 server

Site 2: Total cost $80,000 USD
web server - Dual 2.8GHz processors, Dual Seagate 18GB 15K RPM
drives in RAID 1, 2GB RAM - Windows 2003 server
report server - same as web server
database server - Quad processor 2.5GHz Xeon processors, 4 36GB 15K
RPM drives in 2 RAID 1 configs, 4 GB RAM - Windows 2003 Enterprise Edition -
holds the db logs
Dell powervault with 6 36GB 15K RPM drives in RAID 5 to hold the
database

Now the kicker. Both sites run EXACTLY the same speed. They are not slow,
they are both very fast, but, much to the chagrin of the customer, they are
just the same speed. The key is that both sites obviously have the same
bottleneck. The slowest component will be the bottleneck of any system. In
this case, we believe the bottlenecks are either RAM on the database server,
the RAID 5 drives that hold the database or both. For site 2, the
customer's internal staff was sure that putting the OS one one drive system,
the database log on another drive system, and the database itself on the 6
drive RAID would give a huge speed boost. Like I said, it did nothing for
speed.

So, they key is to spend your money on RAM and drives, make your drive
configuration at least a 5-drive RAID, buy the fast 15K RPM drives, and
don't worry about processor speed much (although I still recommend dual
processors).

Hope this helps,
Best regards,
Chuck Conover
www.TechnicalVideos.net



[quoted text, click to view]

Bruce Lester
2/21/2004 1:49:51 PM
I am looking for advice on what people recommend for a SQL-2000 EE data
warehouse server.

The box would be dedicated to nightly ETL from DB2, generated daily reports,
and ad-hoc queries. We hope to route most queries through Analysis
Services.

We have a $ 20k budget for hardware and around 200 potential users (20
concurrent at peaks) of the data warehouse.

Are people using 64-bit boxes/windows/SQL?

Thanks

Bruce Lester
2/21/2004 9:57:02 PM
Chuck, thanks for the information on the server bottleneck.

As far as storage is concerned, we have already purchased and installed a
Netapp SAN which has been configured to stripe over several drives (at least
5).

One article I read in SQLMAG suggested that Analysis Services should be on a
64-bit platform and that it was CPU bound.

It seems that tuning for SQL Server's relational database is one thing while
Analysis Services is a very different other.

Thanks again for your input.

Bruce Lester

[quoted text, click to view]

Greg D. Moore (Strider)
2/21/2004 11:21:38 PM

[quoted text, click to view]

Given the differences in CPU, memory and changes to disk I'd say the
bottleneck might be someplace else.

We just made a code change (as strange as it sounds wrapping a stored proc
call into an sp_executesql inside a call to EXEC) that more than doubled our
server capacity. Load that we used to have to share between two fairly
similar servers now appears to be able to run on ONE server and still runs
faster. (We're still doing load testing with the new code.)

Basically we were seeing huge amounts of compile locks.

So it might be something like that.


[quoted text, click to view]

AddThis Social Bookmark Button