I am running FME Desktop 2018.1 in a Windows 10. My source data is in a SQLServer database (2016 R2) and the destination feature class is in an ESRI Enterprise Geodatabase (ver 10.5.1) also using SQLServer (2016 R2) as the backend database.
The destination feature class is in a Enterprise spatial data warehouse, business decisions are make on the contents in the destination feature class.
I have a FME Workspace that reads a table with latitude and longitude and writes to a feature class in a ESRI Enterprise Geodatabase.
The writer is set to TABLE Exists: 'yes', TRUNCATE Table First: 'yes'
It appears that FME:
1) Truncates data in the destination feature class, then
2) Reads the source table, then
3) Writes to the destination feature class.
Is this correct or have I misinterpreted the FME log files? If this is correct, then there can be considerable time when the destination feature class is empty or being updated.
If FME does truncate the destination data first, then can I change the order so that FME:
1) Read the source table, then
2) Truncate the destination feature class. then
3) Write to the destination feature class.
The problem is that truncating a feature class with 500,000 points is very quick in my environment (3 seconds), reading the source table can take 2-3 minutes, writing to the destination feature class can take 1 minute. Changing the order may speed up the update process considerable.
