It turns out that we are implementing a new data synchronization scheme in which each branch transmits the news by doing INSERT / UPDATE / DELETE.
The issue is that when there were few branches, there is no problem, but today among all the branches and work positions, there are more than 200 and the server pulls the error mentioned in the title.
What can be done to get around this problem?
The server is a Windows Server 2008, 8GB, and is usually at 10% CPU usage and 15% memory.
The system that transimite is developed in VB6 and makes a persistent connection.