Skip to main content
Question

SQL Server Reader locking table

  • August 20, 2019
  • 1 reply
  • 52 views
fmelizard
Safer
Forum|alt.badge.img+21

I have multiple FME workbenches that read from a single SQL Server Spatial Database. This is a global database so I often have more than one workbench trying to access the database. However, it seems like the first workbench is locking the table preventing others from reading from it. This seems more likely to be an issue if the SQL table has triggers enabled.

Is there away to get around this problem?

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.

1 reply

david_r
Celebrity
  • david_rCelebrity
  • August 20, 2019

If it's the triggers that locks the table, you'll have to fix the problem on the database side.

You could potentially use the parameters "SQL to execute before/after translation" to disable the triggers before reading and enabling them when you're done, but I would usually recommend against it since any failure in the workspace might leave the triggers disabled indefinitely.

Community Stats

32,182
Posts
122,176
Replies
39,855
Members

Latest FME

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.