Skip to main content
Solved

Upsert - recommendation on how to use?

  • April 10, 2026
  • 1 reply
  • 39 views
vxn43
Enthusiast
Forum|alt.badge.img+20

I have an address feature class in a SQL Server 2022 Enterprise Geodatabase. 

Some records have been updated in the attribute table and new records have been added. 

I want to write these updates and additions to another Enterprise Geodatabase and a File Geodatabase. 

Would the recommended approach be to use a ChangeDetector before each Writer and then use Upsert in each Writer?

OR 

Can I use Upsert in each Writer without using ChangeDetector?

 

Currently, the way I do this is to Truncate Existing in the Writer for the Enterprise Geodatabase and the Writer for the File Geodatabase. But, this can take a long time to run. It seems more efficient to use Upsert.

Best answer by hkingsbury

Depending on the volume of features, it still may be worth running the change detector first.

Upsert works on specified ID, if the ID exists, an update happens, if the ID doesn’t exist, an insert happens.

It doesn’t check any other attributes, so you’d be running an update against a feature that doesn’t need updating with the same values/geometry

1 reply

hkingsbury
Celebrity
Forum|alt.badge.img+70
  • hkingsburyCelebrity
  • Celebrity
  • Best Answer
  • April 12, 2026

Depending on the volume of features, it still may be worth running the change detector first.

Upsert works on specified ID, if the ID exists, an update happens, if the ID doesn’t exist, an insert happens.

It doesn’t check any other attributes, so you’d be running an update against a feature that doesn’t need updating with the same values/geometry

Community Stats

32,527
Posts
123,530
Replies
40,749
Members
Terms & ConditionsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.