So I am new to EasySync, and trying to get the best from it.
I am using it more to replicate a subset of a live database for external clients to access, but they will not be changing anything, so my only requirement is to pull data to my 'Mobile' dataset from my 'Hosted' dataset.
At the moment the live database is approx. 120k records, but this grows daily between 100 and 300 records for the main customer view, and possible 3 times that for associated activity.
I seem to have a serious speed issue, in that trying to sync the mobile version just locks everything up, trying to do an initial sync.
I can manually pull the data over at the end of a day, then mark all of these as EX_Exclude 1 and import them manually into my new portal
Set a OnCommit on the maincustomer view, so any changes will make the ES_Exclude to 0, thus marking these for sync
Question 1: How do I set these back to 1 once the sync is done?
Question 2: Is there a way to Schedule the sync to happen every 15 minutes so it has lessto sysnc, meaning less traffic?
Question 3: If I cannot schedule it, how do I prevent the 2 database's from appearing to lock, preventing users from working on either side, or slowing everything down?
Any help with this would be very appreciated as I am totally stumped at the moment.
The attempt to push data to the server has failed. (The message received from the server was: "111A01C0-27AE-414B-AC1C-DC56C83F877EBy Gianluca D'Aquino
I've set up 2 files syncing with Easysync. I've set up just a single table in sync called ES_TRIP (without pull or push, because I want to sync in both directions, is that correct).
I put the same cfg on mobile and on host file and the process start working but it throws me an error:
"The attempt to push data to the server has failed. (The message received from the server was: "111A01C0-27AE-414B-AC1C-DC56C83F877E"
The hosted file is on a fm server 15 that is reachable and working - I've tried the hosted link and it is correctly working.
The TRIP child table is set to add record (but not delete) on both files.
What should I check on it?
Let’s say we have two related tables: “Invoice” and “Invoice_Item”. We could create a calculation field in the “Invoice” table called “total_amount” with this formula:
total_amount = Sum (Invoice_Item::amount)
This field would have a negative impact in performance when appearing in the layout, since it would have to be defined as unstored, because it’s referencing a field from a related table.
Now let’s suppose this field is not used for any scripts, tooltips, conditional format, etc … would the performance of the database be negatively affected ONLY when this field appeared in a layout?
In other words, would adding an unstored calculation field to a table involve a performance penalty, even in the “unreal” case where this field didn’t appear in any layout, script, conditional format, etc.? thanks in advance!
Is there any difference in terms of performance between a calculation field (stored and indexed) and field defined as auto-enter calculated value (indexed)?
For example, we have an “INVOICE” table, with a field called “date_invoice_sent”, and we’d like to have a boolean field called “is_sent”.
The calculation would be “not IsEmpty(date_invoice_sent)”
So we have two options here:
- Calculation field (stored, number result).
- Number field defined as “auto-enter / calculated value / do not replace … unchecked”.
Would there be any difference in performance between the two options? thanks in advance!