1. Home
  2. Point-Of-Sale Software
  3. Performance, hardware, best practises

Performance, hardware, best practises

Hello, We have got Headquarter's database on one computer with SQL2000 installed. HQ Manager and HQ Server is installed on different computer (Celeron 3Ghz -

2Gb RAM).

There are more than 30 stores and there will be much more. We also use items with 3 dimensions connected to matrixes so there are more than 49.000 items in the database. (table Item - 49.000, table ItemDynamic - 1million records !!!). We also have to transfer journals for our 3rd party accounting program. Connection from stores is hour by hour to have the most refreshed data in the HQ. I've read Optimizing_HQ_Performancev2.pdf but I couldn't find information I need.

The questions are:

  1. What can we do to improve performance?! IS HQ Server installed on different computer than SQL server a bad idea?! SQL Server seems to work fine but HQ Server causes the freezes on the computer with HQ Manager. Is the computer with HQ Server the most stressed when using RMS and sending worksheets?!
  2. Creating raports causes to HQ Manager to freeze (maybe also HQ Server is responsible). Which computer is stressed during report creation (Server or HQ manager. Creating them takes ages - the worst is Items - Item Movement Report.qrp)
  3. What maximum hardware configuration we can use to improve performance? How much RAM can RMS use and what kind of CPU's can be used. Is it possible to use 2, 4 core processors? I think that hardware improvement can be my only solution.

Thanks for any help and

Reply to
Hubert Mikołajczyk
Loading thread data ...
1) HQ Server installed on a separate computer from SQL Server is actually a GOOD IDea. In fact, you might consider installing multiple instances on differennt computers to scale that part of the woukload out. Use a gigabit network to connect your HQ Server processors to the SQL Server.

2) Everything is stressed, but Manager and your network connection are probably the bottlenecks. You can find tons of advice on optimizing SQL Server from both a hardware and software perspective. Adding RAM to the machine running HQ Manager is probably the best thing you can do to improve report performance (unless your SQL server is under powered). Also using a gigabit network between HQ Manager and SQL Server may improve performance somewhat, but the biggest challenge is still going to be the fact the RMS Reports load the entire returned dataset into memory.

3) For HQ Manager, RAM is really limited by your OS and Hardware, not the application itself. Most workstations on 32bit windows will not recognize over ~3.5GB. Note of the RMS applications are multithreaded, so multiple processors are not going to privide the kind of boost you might expect. You may get some advantage when running multiple apps (HQ Manager, Word, Excel, IE), but if HQ Manager is the only thing running it's not going to get a big speed bump from multiple processors.

For report performance in your environment, I would seriosly consider abandoning HQ Manager for reports. There are many reporting applications that will allow you to build better performing reports that give the same (or even better) information - pick your favorite (SQL Server Reproting Services, Crystal, MS Access, the list goes on...)

Best of Luck!

Reply to
Glenn Adams

Thank you for your answer.

1) I have read on the newsgroup that it's not recommended to use more than one HQ Server to make network-balancing. Is that right?! Are there any side effects of that solution?! 2) My HQ Server during work use 100% of my CPU. Is there a CPU that can cope with that application?! So the hardware answer for my problems is 3.5Gb RAM and stronger one core processor or use 64bit system and even more RAM. Is that correct?!

Thanks for the > 1) HQ Server installed on a separate computer from SQL Server is actually a

Reply to
Hubert Mikołaj
2x?XMsÛȽãW?Y?[-KÊÖf½µ.¯ìX¬²"?ãÊik ?1
Reply to
Glenn Adams

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.