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.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 paging and memory concerns

Author  Topic 

jamie
Aged Yak Warrior

542 Posts

Posted - 2005-10-19 : 04:47:01
Hi,
I have a sql2000 server with 1 5gig database with 60 users.
I have noticed the server is paging quite alot.
The server currently has 1 gig of RAM and a 3 gig pagefile and is a dedicated SQL server.
Do you think the issue is with the server not being powerful enough or could it be poor application design ?

regards,
Jamie

jamie
Aged Yak Warrior

542 Posts

Posted - 2005-10-19 : 05:27:59
I'm thinking poor application design just noticed the aplication take exclusive locks on the tempdb.. why would someone do this ?
Go to Top of Page

mcrowley
Aged Yak Warrior

771 Posts

Posted - 2005-10-19 : 09:35:14
The exclusive locks in tempdb may be normal. I would expect them, if the application relies on temp tables, or table variables.

How are you defining "paging quite a lot"? Which Perfmon counter, and what is the value?

Also, are there other applications running on this server, or is it a dedicated SQL box?

One thing to check, to see if the application performs well, is to use Profiler, and see if you have lots of queries that have more than 1000 reads or so (just to name a number, no science behind it). Large numbers of reads per query can imply table scans, which are bad.
Go to Top of Page

jamie
Aged Yak Warrior

542 Posts

Posted - 2005-10-20 : 07:28:29
I am viewing pages per second.
I am also using spotlight. this is showing problesm every 20-30 mins.
pages/second are being moved from virtual memory to physical RAM. and vice versa.
This is a dedicated SQL box.


Go to Top of Page

mcrowley
Aged Yak Warrior

771 Posts

Posted - 2005-10-20 : 09:14:15
What does Profiler show you?

And paging is only a problem once every 20 minutes, or for 20 minutes at a time?

Also, have a look at your cache hit ratio to see if it is still in the 90's. I would expect 99 for a database this size.
Go to Top of Page
   

- Advertisement -