+17I 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?
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.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
