Just installed SQL 2000 (SP3) onto a 2003 server. The new server is (right now) single processor 2.8 Ghz, 1.5 Gb Ram 72Gb drive space (grunting like Tim the toolman). The old sever is dual 400 Mhz processors running 2000, sp3 (os and SQL) 750 Mb RAM, 18Gb storage (not free but total). When we moved the data base over from old to new. The queries went from 6 seconds on the old server to 34 seconds on the new server. I have a second processor that had been backordered but I am wondering if that will at least get me to where the old server is right now. I cannot imagine that the new sever would be slower. 2003 is supposed to be 65-70% faster than 2000. Combine that with almost three times the processor speed (even when combined) and almsot double the RAM and it is still slow???? Any ideas????
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Slow SQL 2000 server running on 2003
- Thread starter tpulley
- Start date
Many things can affect the performance. Just because the machine has more resources does not mean that SQL will automatically be faster are the server and sql configurations the same? Are the drive size and raid types the same? are the new drives SCSI or SAN Fibre? Has any SQL configurations been changed on the new server, and do they differ from the old server.
The size of the hard drives and raid type can have a major impact on performance. Many people argue that todays larger faster drives provide the same access speed or better to the data on the drive as having a raid of smaller drives. I have seen first hand where this arguement is not always true.
The number of processors will also have an impact to what degree you really can't say. Do the new processors Hyperthread? if they can are they currently hyperthreading.
Filegroups can also affect performance. if the file groups were created in a manner as to be optimum for the old server may have a negative impact on your current server configuration.
SQL Server BOL has some nice info in regards of performance monitoring and tuning. While not the best it is probably a good start. I'm sure others here can recommend other resources.
"Shoot Me! Shoot Me NOW!!!"
- Daffy Duck
The size of the hard drives and raid type can have a major impact on performance. Many people argue that todays larger faster drives provide the same access speed or better to the data on the drive as having a raid of smaller drives. I have seen first hand where this arguement is not always true.
The number of processors will also have an impact to what degree you really can't say. Do the new processors Hyperthread? if they can are they currently hyperthreading.
Filegroups can also affect performance. if the file groups were created in a manner as to be optimum for the old server may have a negative impact on your current server configuration.
SQL Server BOL has some nice info in regards of performance monitoring and tuning. While not the best it is probably a good start. I'm sure others here can recommend other resources.
"Shoot Me! Shoot Me NOW!!!"
- Daffy Duck
- Thread starter
- #3
The drives are 15K rpm, vs 7500 Rpm drives on old server. Both are on an raid 5 array. How can you tell if a processor hyper threads? I have selected (tried it both ways) to allow fibers etc. I did realize that SP3 was not applied as I had thought. I hope that is the culprit. Let ya'll know, as soon as I know.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
