Skip to main content
  • EN
There is an option SQL Statement to Execute before Translation on the writer side.

 

 

I have a fairly complicated T/SQL stored procedure that prepares the source data. I don't really want to bother adding all that complexity to my workspace. It would be a lot of work and besides, the current procedure works fine.

 

 

When does the execute SQL Statement Before Translation on the writer execute?

 

 

Does it execute before anything else happens?

 

Or does it execute after the rows have been read before any translations have been executed?

 

 

Is there any way, within the workspace, to execute the stored procedure before the readers read any records?
Hi,

 

 

If I'm not mistaken, the "SQL statement before translation" is executed before the first feature hits the writer. That might well be after one or all features have been read.

 

 

I think you should consider the Python startup script, or a separate workspace using a Creator -> SQLExecutor with your stored procedure -> WorkspaceRunner for the workspace that reads your records.

 

 

David

Reply


Community Stats

30,351
Posts
115,341
Replies
38,081
Members
Terms & ConditionsCookie settings
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.