Network Guy
join:2000-08-25
New York
 ·PHONE POWER
·Broadvox Direct
 ·Verizon Online DSL
| MS SQL 2000 performance
Alright, so where I work we run an electronic medical record (EMR) interface called Misys Homecare. This thing is made of several modules in ASP.NET, .NET and whatever other platform it uses to manipulate and exchange patient data to field nurses, clerical staff, etc.
This runs on two semi-old Dell Power Edge 2600s; Dual Intel Xeon 2.8GHz, 3GB RAM, RAID5 array with four Seagate 37GB drives.
As of lately this application is starting to drag when opening patient files. SQL daemon alone is using 1.7GB of memory. There's roughly 450MB of free physical RAM available, but there's lots of paging going on.
I would recommend adding memory, only problem is that the box runs 2003 Server Standard and I'm pretty sure Misys won't run in a 64-bit environment.
What to do?
Help, please.
TIA |
|
Heterman
Premium
join:2004-02-28
Fayetteville, AR
| First, do you have SQL and IIS running on the same box? SQL Server should be on a dedicated machine if at all possible. The way SQL Server works is to gobble up RAM as needed, making the cached data available fast. You can configure it to use a set amount through Enterprise Manager (generally not recommended). More info: »support.microsoft.com/default.as···;q321363 |
|
McSummation
Mmmm, Zeebas Are Tastee.
Premium,MVM
join:2003-08-13
Round Rock, TX | reply to Network Guy
Is there such a thing as "defragging/compressing" the tables on SQL 2K? There is in Access and if you let a heavily updated table get fragged it will slow down the access times. |
|
