Hi @michael_m,
I'm not sure if you still have this problem, however, there is this article which might be useful:
https://knowledge.safe.com/articles/165/improving-performance-when-working-with-esri-geoda.html
In General I would say SDE is a bit slower than File Geodatabase, however, what you are describing is painful. One thing which you can check in the logfile is the difference between CPU usage vs FME Session duration. If the CPU is very low compared to Session Duration then it means FME is waiting. This could be due to slow network or a particular configuration of the SDE itself (e.g., versioning) or the writer configuration (transaction type).
Another thing which I've seen is due to limited permissions - As I remember there were cases where the Feature type had it's table handling to Truncate Existing, however, the user didn't have permission to truncate so and edit session was started and each feature was deleted one by one....This doesn't sound like you though because from the sounds of it you are just trying to create them and fill them up.
If you are really not making progress then I would get as much information about your environment as possible form IT (FME version, 64 bit vs 32 bit, ESRI version, underlying Database version etc) and send a reproduction to Safe Software along with the logfiles and workspace you have. They can try and reproduce your issue or, at least, rule FME out of the picture.
Good luck.
Hi @michael_m,
I'm not sure if you still have this problem, however, there is this article which might be useful:
https://knowledge.safe.com/articles/165/improving-performance-when-working-with-esri-geoda.html
In General I would say SDE is a bit slower than File Geodatabase, however, what you are describing is painful. One thing which you can check in the logfile is the difference between CPU usage vs FME Session duration. If the CPU is very low compared to Session Duration then it means FME is waiting. This could be due to slow network or a particular configuration of the SDE itself (e.g., versioning) or the writer configuration (transaction type).
Another thing which I've seen is due to limited permissions - As I remember there were cases where the Feature type had it's table handling to Truncate Existing, however, the user didn't have permission to truncate so and edit session was started and each feature was deleted one by one....This doesn't sound like you though because from the sounds of it you are just trying to create them and fill them up.
If you are really not making progress then I would get as much information about your environment as possible form IT (FME version, 64 bit vs 32 bit, ESRI version, underlying Database version etc) and send a reproduction to Safe Software along with the logfiles and workspace you have. They can try and reproduce your issue or, at least, rule FME out of the picture.
Good luck.
Thank you, @virtualcitymatt. It did turn out to be the setting for "Transaction Type". I changed that from "Versioned Edit Session" to "Transaction" and the overall write time fell back to about two hours.
