HQ Client Schedule

I've got to come up with a schedule for four stores. My initial plan was to have each store connect hourly, each at a different quarter hour. Today we had a customer stop at store 3 and buy some stuff then promptly drive to store 2 and buy more stuff. When the folks at store 2 searched for an existing customer account, of course they didn't find one.

I'd like to have the stores connect three times per hour - every twenty minutes, with 5 minutes for each store. :00, :20, :40 - :05, :25, :45 and so on.

Tom

I don't want to specify the duration of the Store/HQ session.

I was under the impression that multiple simultaneous connections were not good. I figured that 5 minutes was plenty of time to have the first session complete before the second session began.

If multiple simultaneous connections aren't taboo, then you are correct. I will start having everyone connect much more often.

Thanks for the advice, Tom

"Jeff" wrote:

minutes, it talks until its finished.

every minute, at the same time, if you want.

up/download, it will check a minute after it finished the previous up/download... ;-)

watch the HQ Client log. 5 minutes transfers _a lot_ of data back and forth.

I must have missed that one. I did take a nearly two-week vacation at the beginning of August. The message is no longer on my news server, so if you could re-post or e-mail it to me, I'd appreciate it.

I changed my schedule so that the four stores connect every 3,4,5,6 minutes respectively. This will result in a fair number of multiple simultaneous connections, but since my hardware is almost exactly as you describe the MS test h/w, I doubt I'll have any trouble.

Thanks for the reassur> TT,

stores. With your 4 stores and a dedicated server, no problem. ;-)

transfer per connection.

people a while ago? In that, they were testing _40 stores_ connecting at the same time with 1.2. Course it work crash HQ Server after about 2 days. They never did test it on 1.3 the same scenario. They chickened out and only did 50 stores on a staggered schedule. I did _not_ crash after 8 days. They only used a

3 GHz Xeon and 1 gig of RAM. If you did get it already, its described in the last 5 pages or so.

minutes, it talks until its finished.

connect every minute, at the same time, if you want.

up/download, it will check a minute after it finished the previous up/download... ;-)

to watch the HQ Client log. 5 minutes transfers _a lot_ of data back and forth.