Skip to main content
Solved

Trying to use SQLCreator or SQLExecutor with a workspace runner to run a SQL Stored procedure after upload completion

  • November 1, 2016
  • 2 replies
  • 92 views

brady
Contributor
Forum|alt.badge.img+1

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

Best answer by todd_davis

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

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.

2 replies

todd_davis
Influencer
Forum|alt.badge.img+23
  • Influencer
  • Best Answer
  • November 1, 2016

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


brady
Contributor
Forum|alt.badge.img+1
  • Author
  • Contributor
  • November 1, 2016

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