Skip to main content
Question

SQLExecutor No Longer Working

  • August 26, 2026
  • 2 replies
  • 88 views

spawkly
Participant
Forum|alt.badge.img+7

I have a workspace on FME Flow that ultimately creates records in a SQL Server non-spatial database using two SQLExecutor transformers with queries that came directly from the DBA.  I didn’t write the queries and I only basically understand what they do because I’m not a SQL person, but they both are sandwiched between “BEGIN TRANSACTION  → COMMIT” statements.  

Up until recently, the SQLExecutor transformers in question used hard-coded server/username etc and it all worked fine.  However, during our most recent FME Flow software update (to 2024, but I don’t think Flow is the problem here as it is present in my Form testing as well) I was informed by our FME administrator that I could no longer use hard-coded server/username details, I had to switch to using an ESRI ArcSDE Geodb connection file to connect to this SQL Server database.  

This change worked just fine for other, more simple, Select and Insert sql queries, but these two mentioned above just stopped working.  

I confess I find myself completely stumped.  There are no error messages, they simply don’t produce the expected results in the database.  If I switch back to hard-coded passwords, it all works fine again.  The queries haven’t changed and the connection file was created in ArcGIS Pro using the same details.  

Can someone point me in the right direction on how to fix this?

2 replies

veronikaatsafe
Safer
Forum|alt.badge.img+9

Hi ​​@spawkly,

Are you able to share your full FME translation log with debug enabled covering the run where the SQLExecutors are meant to write the records? It would be very helpful if you could share your SQL statement as well.

Thank you!
 


j.botterill
Evangelist
Forum|alt.badge.img+69
  • Evangelist
  • August 27, 2026

Yes embedded credentials are less secure than database connections. You can make a MS SQL database connection for the existing two SQLexecutors, rather than using ArcSDE connection, which will parse its on SQL code to extract featureclasses.

 

In the SQLexecutor choose format reader Microsoft SQL Server, then in Connection select Add Database Connection. Enter:

  • Server
  • Database
  • Authentication: either SQL Server Authentication or Windows Authentication
  • If using SQL Server Authentication, also enter Username and Password

You can also create it from Utilities > FME Options > Database Connections > Add. SQL Server connections in FME typically do not require a port unless your setup specifically does.