Windows Server Enterprise and/or x64 editions at RMS

Hammered how? Busy disks, RAM consumption, CPU, network?

You probably want to put HQ server on a seperate machine

Cheap and very functional option: XP PRO or Vista desktop with 3 GBs RAM and HQ server Waste of money option: Windows Server Enterprise Edition or Std Ed. x64 with more than 4 GBs

Where is HQ client located?

I have learned from my reseller that no x64 OS is supported. Enterprise Ed. is out of the question due to the crazy price. 4GB max RAM for Windows Server is pathetic.

Hammered = CPU utilization practically never 70% for hours at a time. RAM consumption is also not very efficient. SQL server will gobble up RAM until it's using nearly 2GB, sometime more. Disks seem to be OK.

HQ client is on a desktop PC. Store Ops and HQ are on the same server, three remote locations where HQ client in on the Store Ops server.

I am beginning to think that part of my problem is Small Business Server. I am getting rid of it. I have ordered a new server--quad core Xeon, 4GB RAM, RAID5 to host the HQ DB and will keep the Store Ops DB on the current server. I may move HQ client to the Store Ops server, though it is convenient to have it on a desktop PC.

My configuration has not changed, but the application of HotFix 2.0.0115 has

I have revised my connection schedules so that no two stores are every connected simultaneously and that has helped.

Tom

We have just installed the new hotfix for a group of 40 stores and it has slowed down our store comms from about 15 minutes to around 4 hours to process worksheets. The SQL server and the HQ Server boxes have plenty of ram and are both maxed out for around 8 hours a day. Our IT supplier has no idea what the problem is and is suggesting we put in another server to balance the workload.

Well, it's good to hear that I am not alone.

I love that MS puts out a HotFix that can diminish performance dramatically (15 minutes vs. 4 hours for the same task?!?!?!?!) and not even give you a heads up about potential performance issues in the ReadMe file.

I have a new server on order and have just started paying an additional $100/month for increased bandwidth at the HQ location. It's getting better with the increased bandwidth, and the new server will allow me to move HQ to dedicated box.

This is a sad story.

I have learned from my reseller that no x64 OS is supported. Enterprise Ed. is out of the question due to the crazy price. 4GB max RAM for Windows Server is pathetic.

Hammered = CPU utilization practically never 70% for hours at a time. RAM consumption is also not very efficient. SQL server will gobble up RAM until it's using nearly 2GB, sometime more. Disks seem to be OK.

HQ client is on a desktop PC. Store Ops and HQ are on the same server, three remote locations where HQ client in on the Store Ops server.

I am beginning to think that part of my problem is Small Business Server. I am getting rid of it. I have ordered a new server--quad core Xeon, 4GB RAM, RAID5 to host the HQ DB and will keep the Store Ops DB on the current server. I may move HQ client to the Store Ops server, though it is convenient to have it on a desktop PC.

My configuration has not changed, but the application of HotFix 2.0.0115 has *really' hurt HQ Client/Server performance.

I have revised my connection schedules so that no two stores are every connected simultaneously and that has helped.

Tom -- Stop fishing for e-mail

"Frederic Hurlet" wrote:

After meeting with out IT vendor, we are now putting in 2 x comms servers for HQ server (each running 20 stores), a new SQL server (apparently a dual core xeon 1.86 is not sufficient for RMS SQL), and a new citrix application server for HQ manager. All in all, we have now spent almost 3 times in servers what Microsoft advised would run RMS just fine (we have gone from 2 servers to 5 servers). And we have now been advised to upgrade all the store HQ client pc's aswell, since HQ client apparently cant run on a celeron processor.

Basically microsoft grossly misrepresented the recommended hardware specs for HQ and store setups. Hope your new server addresses your issues.