Please start any new threads on our new site at We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 How to improve the performance of New Server

Author  Topic 

Posting Yak Master

202 Posts

Posted - 2006-06-05 : 07:20:14
Hi guys,

I am new to SQL Server administration, Today, we have installed a new sever with the follwing configuraion.

CUP Speed-6GZ.

in this server , we have a database of size 50GB
Could u tell me various server propertis i can set to improve the
performance of the database.

Thanks in advance.


22859 Posts

Posted - 2006-06-05 : 12:10:24
Hardware check first:

Split the disks into 3 or 4 separate channels:

0 = O/S
1 = Data
2 = Logs
3 = Backup files

Use RAID1+0 instead of RAID5 for data and logs

You should have 2CPUs minimum, 4 CPUs or more if the DB is CPU intensive.

For SQL Server (2000) to use more than 2GB RAM you need Enterprise Version of both SQL and the O/S, and some special settings for the hardware.

Application / DBA check:

If you have done all of that already then its down to optimisation of the queries, good housekeeping for defragmentation of indexes, updating of statistics and recompilation of SProcs etc. that slow down over time.

You should also be creating a disaster recovery plan.

As you mention "I am new to SQL Server administration" I expect that lot is a pretty big stretch (if it was my server I'd be looking for someone with 3-5 years experience, assuming a high-demand system).

But feel free to ask any specific questions for problems you come up against.

Go to Top of Page

Starting Member

5 Posts

Posted - 2006-06-05 : 13:57:26
*** "You should have 2CPUs minimum"

is having a dual core CPU equivalent?

thanks, wkl
Go to Top of Page


22859 Posts

Posted - 2006-06-05 : 14:16:27
"is having a dual core CPU equivalent"


Go to Top of Page

Norsk Yak Master

3271 Posts

Posted - 2006-06-05 : 16:51:04
Have your developers use WITH (NOLOCK) is my contribution. All selects cause locking of data and at least in my company 98% of queries are on historic or non-critical data. The performance-increase on an intense system can be dramatic. Syntax:
FROM table 1 a WITH (NOLOCK)
ON a.ID = b.ID
I'm aware that this is not exactly what you asked for but since I'm not a hardware-person this is what you get

"Real programmers don't document, if it was hard to write it should be hard to understand"
Go to Top of Page

- Advertisement -