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 |
|
sigpop
Starting Member
6 Posts |
 Posted - 2006-01-27 : 12:41:01
|
| i expect this to be some sort of configuration issue. the stored proc runs under two seconds on other computers in our company. on mine it takes over 90 seconds in query analyzer. the stored proc does access a view that joins in a partitioned view which has quite a bit of data. no lock hints are used.my computer has 1 gb of ram and 3.2 ghz intel cpu. other computers are similar in configuration.my memory settings for my server are Dynamically configure SQL Server memory. min setting is zero and i changed max setting down from 1022 to 866.when i look in the task mgr, i notice total memory usage exceeds 1 gb (so it must be using virt memory).any suggestions where i can look? i did just order another gb of ram, but would like to solve the problem prior to installing it. |
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2006-01-27 : 13:09:35
|
| In QA, the query is NOT executing on the client...it is executing on the server. there should be NO difference in execution times on by client...unless there are 'different network speeds' for returning the results to the different clients.We would be interested to see the execution plans for each execution of the query...ie 1 from the slow pc and 1 from the fast pc. |
 |
|
|
sigpop
Starting Member
6 Posts |
Posted - 2006-01-27 : 13:25:33
|
| i should have been more clear. it runs fast (enough) on two other servers, but on my server it takes far too long. i am testing using query analyzer locally on each server. the db we are using was restored to each machine.when i checked the exec plan, the are definitely different. i find that odd. i would have expected identical results there.i'm not sure my boss would allow me to post the specific exec plan. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-01-27 : 13:34:07
|
| Have you tried recompiling the stored procedure?Tara Kizeraka tduggan |
|
|
|
sigpop
Starting Member
6 Posts |
Posted - 2006-01-27 : 14:09:21
|
| good idea, tarra. i ran exec sp_recompile on it, then tried a re-run. still takes too long.more info on the virt memory/page file: in task mgr, it shows the total under PF Usage as 1.3 gb. since i only have 1 gb of ram, does that mean it's using .3 gb swap file on the hard drive? if i restart, everything that loads up consumes about 500 mb. after running the qry, i see it climb back up to 1.3 gb. i have sql server clapmed at 850 mb. |
|
|
|
sigpop
Starting Member
6 Posts |
Posted - 2006-02-01 : 14:42:29
|
| 2 gb of ram did not solve the problem. cut down on page file access on my hard drive, which is nice. but the qry still takes 30 secs. i'll prob try to reinstall sql svr next. |
|
|
|
|
|
|
|
|
qry times out on one computer, not another