Hi All
May I know 1 HQ Server can handle how many concurrent HQ Client can connect to update data?
because currently if more than 5 HQ Client concurrent connect to 1 HQ server.
The program will look like hang, then may prompt show the message "Connection to socket was unsuccessful: Message Timeout"
How can i judge the what kind of PC specification should use to handle at least 10 concurrent connection?
hope anyone can give me some hint and help.
Thank You
*This post is locked for comments
Hi DR.RYU, Jeff , SDDXB and other.
Thank You
After i recheck again. i found the problem actually is data locking.
my customer have 90 outlets now. and they prepare 6 gateway to sync data
Now i used SQL command sp_who or sp_who2 to check data locking.
I found when few outlet sync concurrent but different gateway it can make the data locking.
How can i solve the problem ?
Open 1 gateway only and adjust the time?
Thank You for any suggestion and help.
There s a solution to increase the number of HQ servers so simultaneously number of HQ clients can connect.
Time out errors , 401 red flags will be less in this way.
This type of solution required when you have 65+ stores... If you deal with 20 then JEFF answer will work by changing the schedule.
Run a connection and see how long it takes, add a minute or two and schedule them. They don't all have to run at the same time.
Hi NG, I am using 20 HQ Client concurrent to 1 HQ server.
I am using Dell Power Edge T310 with 32G RAM and SQL Server 2008 R2 and Windows Server 2008 R2.
I do not have any major issues using one server but I do get timeout or connection lost few times a week.
You should be fine with 5 stores and if you are using Server OS and SQL Server for your server.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (