Skip to main content
  • EN

Hi all. I feel I am going around in circles.

I have a data update process uploading data regularly to SQL server. A requirement of this update is to run a couple of stored procedures on the uploaded data. I wish to run stored procedures that are entirely internal to SQL server after the upload is complete, rather than having to duck into MSSMS to trigger them. I don't require features or attributes to be passed back to FME.

Currently, I am have embedded my process in a workspace runner and use a single item creator to trigger it. I then hope to have the stored procedure(s) run/triggered from SQLExecutor or SQL Creator (if it will work in this fashion)

Something like exec dbo.'storedprocedurehere' only doesn't cut it. Comes back with a malformed statement.

Any help would be appreciated.

Thanks,

Brady

From your error message, you just need to update the timeout within the SQLExecutor (under parameters). Your stored procedure is taken a while to complete and because FME doesn't get a response in that defined time, the query times out

From your error message, you just need to update the timeout within the SQLExecutor (under parameters). Your stored procedure is taken a while to complete and because FME doesn't get a response in that defined time, the query times out

Hi @todd_davis, thanks for your answer. I have done that and it may very well have done the trick. The process seems to be called now.

 

 

Cheers

 

Reply


Community Stats

30,126
Posts
114,351
Replies
37,758
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.