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 |
|
ay2k_99
Starting Member
22 Posts |
 Posted - 2009-05-14 : 06:58:45
|
| Dear All,We are using BFSI domain to capture the huge amount of data from sql server. During that time when i run the sysprocesses query.. i got the spid for this query CXPACKET is 4 coz i set my server setting max degree par is 4 and ASYNC NETWORK IO is using memusage is 2.. i don't?Actully that specific query was return around 4.5 million rows. and it take 90 min to from client and it run on server it takes 55 sec.what other things to tune i need to know to run this query faster... |
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2009-05-14 : 07:18:08
|
Add proper indexing, avoid character transformation and other good things to know.
E 12°55'05.63"N 56°04'39.26" |
 |
|
|
TRACEYSQL
Aged Yak Warrior
594 Posts |
Posted - 2009-05-17 : 19:42:13
|
| Try setting the query to use one processor see if that helps. I forget the command to use in the query itself. Check the entire script in Profiler and see where it taking the time to run. Does it run at night at a specific time during backups ? Perhaps run it at night when no one on there and do the profiler see where the problem is. |
|
|
|
|
|
|
Network Packet size-- query slow..