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 |
|
seldenm
Starting Member
5 Posts |
 Posted - 2007-07-11 : 20:36:55
|
| I'm pretty new to sql server admin, so this may seem simple... but..I have a dedicated web server (win 2003 server) with 1GB of ram. It runs sql server and also is the web server for 4 web sites. Things run pretty well for several days, then all of a sudden the server slows way down (e.g. it takes several minutes to log in using remote desktop). SQL Server 2000, sp 4.Stopping and restarting IIS has no effect. Only stopping and restarting SQL Server brings things back up to speed.While it's running OK, sql server is using about 500 MB of RAM, and the other processes vary, but typically there's only about 100 MB free. CPU averages around 20%. Both the CPU and memory numbers look about the same when it's in the "slow" mode.How do I troubleshoot this? I know how to run Perfmon, but am not sure what performance counters to look at, or what do do after that.Any advice would be appreciated!---Selden |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-07-11 : 22:41:44
|
| Shouldn't run sql and web on same machine. |
 |
|
|
seldenm
Starting Member
5 Posts |
Posted - 2007-07-14 : 11:51:01
|
| I was really hoping for some helpful advice. Since the db/server run for several days at a stretch without problem, I think it's safe to say the combination isn't taxing the machine too much. What I'm thinking is maybe some process involving the database is either hanging or not releasing memory, etc. Does anyone have suggestions (maybe using perfmon) to troubleshoot this issue? I'm using programs (web site and web services) written in .Net to access the db.Any sort of advice where to get started profiling would be appreciated!Thanks, ---Selden |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-07-14 : 12:56:11
|
| Checked disk i/o, data buffer hit ratio, table fragmentation? Do you set max memory for sql? Update statistics or rebuild index periodically? Other things like total db size, user connections, db process rate, blocking, web hits, many factors.By the way, back to basic. Never a good practice to run sql and iis on same machine since both of them are big resource consumer. |
|
|
|
|
|
|
|
|
Sql Server Brings Down Web Server