The owners of distributed client-server solutions and especially those that were built and deployed years ago eventually face the negative effects of system bottlenecks. These effects may not affect the work of the system for a long time, but as soon as the number of client-server connections and requests crosses a certain threshold, the whole system starts slowing down and becomes less stable. A typical example of such a system would be a client-server solution with a single central database server and a server-side service or application processing data from hundreds or even thousands of terminals that update the main database on a regular basis. Once the data is submitted, each terminal starts sending status update requests to check whether it has been received and processed by the service. These requests generate a tremendous amount of traffic, as they keep coming in while the service dispatches the results of its work on previous submissions. When we are dealing with thousands of client systems, this avalanche-like process eventually assumes the shape of a non-stop DDoS attack that brings the central server to its knees. If you operate a system with a similar structure, you are probably looking for a way to decrease the load on the server and give other server applications a chance to work as planned. If that is correct, take a close look at Database Event Alerter!
Database Event Alerter is a handy database solution comprised of two parts — a server-side function that sends messages to all (broadcast mode) or specific client systems and a client-side OCX control that receives these messages. The software currently supports virtually every popular DBMS, including MS SQL, Oracle, PostgreSQL, Firebird and MySQL. The server function can be called from a stored procedure, a trigger or directly by a user connected to the database server. Activation of the message reception mode is simple — just call the «Listen» method with a subscription identifier as a parameter. This parameter defines whether messages sent by the server to a specific client group defined by the @dest (destination) parameter of the server function will be received by this control. When data is received by the control, it runs the code defined by the developer in the OnData event.
As you see, using Database Event Alerter in a large legacy system suffering from degrading performance can solve this problem with minimal changes to the code. The server will assume the responsibility for broadcasting service information to clients and you will get rid of thousands of unnecessary requests putting a drag on your central database server!
PA Server Monitor 4.0 PA Server Monitor is a Windows service that monitors the health and availability of Windows servers, network services (on Windows, Linux and other operating systems), and devices