Skip to main content
Solved

GEODATABASE_SDE writer ignores table qualifier on 'Create if Needed' or 'Drop and Create'

  • February 3, 2026
  • 2 replies
  • 62 views
artw
Contributor
Forum|alt.badge.img+2

Apologies if this has already been asked - seems like it should already have been reported.

FME Form 2025.0.1
FeatureWriter Version 0
Writing to Esri Geodatabase on MSSQL Server 2019

When using either Create if Needed, or Drop and Create table handling, the geodatabase_sde writer appears to ignore the table qualifier set on the feature type.
 


The table gets successfully created, visible in SSMS - but under the default user database schema eg: domain\john.smith.FeatureClass1
 


However the flow then fails because at some stage it does take into account the table qualifier and is looking for a table called sde.FeatureClass1

An error occurred while attempting to create the table 'sde.FeatureClass1'. The error number from ArcObjects is: '-2147220655'. The error message from ArcObjects is: {DBMS table not found [{dbname}.sde.FeatureClass1]}


The user has appropriate permissions on the sde schema
(Note: It is an Esri requirement that the users default database schema name matches the username, so the default can’t just be changed in SSMS)

 

Best answer by desiree_at_safe

Hi ​@artw 

What version of ArcGIS Pro and the Geodatabase do you have installed?

As a quick check outside of FME: using the exact same .sde connection file, is the user able to manually create a Feature Class named sde.FeatureClass1 directly inside ArcGIS Pro?

It’s possible there’s a mismatch between how FME is instructing the table creation versus how the default schema is being handled; that ArcObjects error -2147220655 (DBMS table not found) is especially interesting.

Would you also be willing to share a full log file with Log Debug enabled first:

 Utilities > FME Options > Translation > Log Debug 

 

    This post is closed to further activity.
    It may be an old question, an answered question, an implemented idea, or a notification-only post.
    Please check post dates before relying on any information in a question or answer.
    For follow-up or related questions, please post a new question or idea.
    If there is a genuine update to be made, please contact us and request that the post is reopened.

    2 replies

    desiree_at_safe
    Safer
    Forum|alt.badge.img+19

    Hi ​@artw 

    What version of ArcGIS Pro and the Geodatabase do you have installed?

    As a quick check outside of FME: using the exact same .sde connection file, is the user able to manually create a Feature Class named sde.FeatureClass1 directly inside ArcGIS Pro?

    It’s possible there’s a mismatch between how FME is instructing the table creation versus how the default schema is being handled; that ArcObjects error -2147220655 (DBMS table not found) is especially interesting.

    Would you also be willing to share a full log file with Log Debug enabled first:

     Utilities > FME Options > Translation > Log Debug 

     

    Happy FME-ing!
    artw
    Contributor
    Forum|alt.badge.img+2
    • artwContributor
    • Author
    • Contributor
    • February 5, 2026

    ArcGIS Pro 3.3.7
    Geodatabase 10.9.1.2.9
    But you’ve probably explained it there ​@desiree_at_safe 

    Using normal Esri processes, tables always need to be created as the dataowner (schema owner), doesn’t matter about permissions.

    So while permissions can allow another user to delete a table, Esri rules means the recreation can only happen from the dataowner account.

    FME obviously doesn’t allow us to get around this restriction - and is a bit of an annoyance if we try to use Drop and Create, from a user account, as opposed to the dataowner account.

    Community Stats

    32,329
    Posts
    123,142
    Replies
    40,359
    Members
    Terms & ConditionsCookie settingsAccessibility 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.