Need Advise - Slow Server???

[LCannon]

I have about 30 clients that are connecting to several servers on my LAN. One of them is a Win 2K server with SQL 2K. Recently, about a week and a half ago, they have been getting times when the programs run that connect to the SQL databases slows WAY down. I'm trying to figure out what the problem is.
First thought it was the server so I moved everything to another, recently rebuilt server, with a fresh copy of SQL 2K. But the problem remains. No hardware has changed. I'm thinking that it might be due to how the clients connect. I've been monitoring the server, FS1, with Performance Monitor and see where the CPU and Index Searchs spike. But the slowness happens when traffic is low, too. Don't know if the CPU or Index Searchs spikes when traffic is low, yet.
Am changing the ODBC connections from Named Pipes to TCP/IP but not sure if that will help. Have read where people say TCP/IP is faster/better.
Am open to any ideas.

 

[gmath213]

I am having a similiar problem. We have about 50 clients and 2 remote site connected through a VPN. After a reboot server runs alot faster but by end of week slows down.

Greg

 

[karsh]

HI
My problem is the same one, we have about 25 clients in a LAN connected to the central (Windows2000)server.
THe most often problem we come across is when we try to explore something it gets hunged up for a while and then explores as per its convinience
this is more frequent with the network drive. there is also enough space on the disk and so as memory. We are connected remotely to a server my DSL line.

any Advise suggestions are appreciated.
Thanks

 

[gmath213]

I moved my Pagesysfile from the C partition to a differnt partition adn sems to have solved my problem.

Greg

 

[LCannon]

It turns out that my problem with my SQL Server was not, at least directly, related to SQL. I have another server connected to it that was having problems with a frame relay connection. The connection was delaying causing that server to work extra hard to keep the connection up. We ended up changing some configurations to allow for the delay and, almost like magic, my SQL Server settled down.