Env: MS SQL Server 2005 developer edition on Windows XP Pro
I have a fairly complex query that create a 'variable TABLE' and then,
run a set of freetext search using the CONTAINS predicate,
and add matches to this table;
and then fetch the matches from the target table.
The execution used to be 1/3 or 1/4 or even less of a second. But
now, all of a sudden, it almost takes 1 second to run it. Nothing
really has changed, be it, the db server, the db or the box itself.
How come? I'm puzzled.
Digging the log files, I found the following entry,
"04/17/2008 03:49:26,spid1s,Unknown,A significant part of sql server
process memory has been paged out. This may result in a performance
degradation. Duration: 374427 seconds. Working set (KB): 8028<c/>
committed (KB): 24288<c/> memory utilization: 33%.
", wtf? I mean, how come?
I ran some similar queries using a query client, speed seems very
good...
Also, could it be caused by some Windows XP automatic update?
(unintended consequence)
Also, I'm using a third party tool for the web presentation, could
some of its service degrade because previously it was good?
Thanks.
|
