I recall reading that IIS (on Windows 2000) and SQL Server should NOT be on the same box. I believe the reason is that each product has a memory manager that wants to manage the entire box. This clash supposedly degrades the box quickly. You may want to see if there is any supporting information on the Web. hth
-brian > Hi everybody... > > I hope this is the best place to post this. I'm running out of options because nobody seems to know what's causing this. > > I have a webserver... it's running Windows Server 2003 with all updates except SP2. It's running MS SQL Server 2000 with SP3a. It's also running CF MX 7. > > This server is running a series of personal websites and message forums, on forum software that I wrote myself about two years ago. There are 6-8 forums running off of the same codebase and database (the URL being the determining factor as to what content is selected). Ever since the forums started getting a lot of use, the server itself has slowed to a crawl. It's a P4-3.0 GHz machine with 1 gig of RAM. > > I'm 99.9% sure that the slowness problem is being caused my SQL Server. When I run PerfMon, I watch CPU utilization, Avg Disk Queue Length, and a few others. The one to note is Avg Disk Queue Length. Whenever this item spikes and maxes out, the system stops responding until the item drops off again. It seems unrelated to CPU usage. These spikes last anywhere from 5-30 seconds, and again while it's spiked, nothing else on the server can take place. In some instances, a remote session with Terminal Services will freeze up; otherwise it just gets really sluggish. > > These spikes go away if I pause or stop the SQL Server service.. but that's kinda pointless since the sites won't run without it. > > There's only one database still in use on SQL Server now -- I've moved the rest to mySQL, on the same box. The one left is the big one -- the one the forums depend on. BUT, my users have said that the system feels less sluggish now. I've noticed it's not as bad either, but it still happens. > > I would go ahead and move this last database, but the migration tools for SQL Server to mySQL are poor at best, at least the ones I've found. It takes several hours to export the data, and then several more to manually modify the SQL code it exports because of bugs in the export script that I've been unable to correct. > > So I'm kinda stuck and unsure what to do next... > > Any ideas? > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:6:2272 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/6 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:6 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.6 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
