Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
mela
Starting Member
2 Posts |
 Posted - 2007-08-24 : 23:39:36
|
| Hi Guys,We currently have two servers, one for development and one for production. As we don't really have any inhouse expert on server, WIN 2003 nor on SQL Server 2000, we just go by the default setting.My problem is that i've noticed once i start to moved all my applications and perl scripts and other background jobs to the new server, there seems to be some performance hit to the database in the SQL server.A very good example is i have a perl script running which executes four queries in a row, one to get the latest id, one to insert into the main table and the other two which insert into two linked tables.Comparing runtime of the script connected to each server shows quite a difference, and sometimes i notice that the script connecting to the production server could be running for a long time after executing the first query.So is there a way for me to check and pinpoint down the root cause here? i.e. do a performance benchmarking or something?thanks!! |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-08-24 : 23:49:52
|
| You can check performance with perfmon and profiler, should check cpu usage, memory usage and dis i/o. Take look at Microsoft knowledge base article 'Microsoft SQL Server 2000 RDBMS Performance Tuning Guide for Data Warehousing' and 'Top SQL Server 2005 Performance Issues for OLTP Applications'. |
 |
|
|
|
|
|
How to benchmark SQL Server performance?