David - we aren't moving large sets of data. Our pull process is pulling data to populate our POS terminals. So we are only pulling products, prices, promotions, inventory, etc. Total record count is currently less than 1000. We are not pulling any transactional data down to the POS terminals so our dataset is pretty finite. It won't grow much.
----- Original Message ----- From: "David E Jones" <[EMAIL PROTECTED]> To: [email protected] Sent: Wednesday, February 20, 2008 12:40:01 PM (GMT-0700) America/Denver Subject: Re: Offline entity sync The Entity Sync stuff is definitely not meant for large sets of data, but rather for trickling regular updates over the line. Part of the reason for this is that it loads all data into memory for sorting records by time and interleaving records from multiple tables (which can't be done with a normal database query) and other such operations. You can, however, do an export to a file with and entity sync ID (from WebTools) and it pulls the data from relevant tables for initial loading into another system, which can then be setup for Entity Sync going forward. -David On Feb 20, 2008, at 12:28 PM, Jeff Burton wrote: > I'm running into a problem where an initial entity sync (pull from > server to POS) in order to load starting data is too time consuming > and doesn't seem to be the best method for the task. I see there's > an offline entity sync service and wonder if this may be more > appropriate approach. What's the quick and dirty explanation of how > this is setup and operates? Thanks.
