Load balancing lets you prepare for scalability and growth to your ServiceDesk environment. Setting up a load-balanced environment requires preparation and planning. It also adds some additional maintenance overhead. You must consider load balancing before installation, upgrades, and updates.
You must set up your load-balanced environment before you install ServiceDesk. You cannot introduce load balancing during or afterwards.
You should plan your implementation schedule to allow for adequate testing. You should set up an environment that resembles the proposed production implementation.
The main reason for setting up a load-balanced environment is that you need additional server resources to keep up with your environment's load.
The following are examples of increased loads:
Each additional installation of the ServiceDesk server, you put more of a load on your SQL server.
The more technicians you have processing tickets, the greater the number of concurrent SQL transactions.
The more process tickets that are generated each day, the more SQL server resources are required. Additional ServiceDesk servers can help to maintain system responsiveness as your usage levels increase.