Hi guys,
I want to know how to run Stored Procedures as DB Inputs in DB Connect 2.
I have some SP's running as DB Inputs in DB Connect 1 and they work great. Also, those SP's receive as a parameter the rising column like this:
EXEC [user].[sp_records_monitor] @LAST_UPDATE = {{ ? }}
But now I'm migrating from DB Connect 1 to DB Connect 2 and I'm getting errors when I define those SP's as a DB Input and also passing the rising column to the SP.
Already tried to run the SP outside, in the search, using the dbxquery, but didn't work either.
Can anyone tell me the exact syntax to run the query now with the SP and also how to pass the value of the rising column to a DB Input?
Best regards,
João Amorim
Hi joao_amorim,
quick update: as of now, this is possible with DB connect v3 http://docs.splunk.com/Documentation/DBX/3.0.2/DeployDBX/Commands#procedure
cheers, MuS
Supported as of v3 for dbxquery which is great, but still not supported as dbinputs, it seems, which was the question
Last I checked, it was not supported on DB Connect. See these posts
https://answers.splunk.com/answers/227133/splunk-db-connect-2-gui-runs-stored-procedure-but.html
There is a workaround though
https://answers.splunk.com/answers/117085/need-to-get-data-from-a-stored-procedure-in-db-using-the-d...
Yeah but at DB Connect v1 I have two DB Inputs that run SP's like i said so probably at DB 1 is already supported.
Thanks for the fast reply
It is not supported in DB Connect 1, you just got lucky that it worked. Maybe try disabling query wrapping on the connection?
@jcoates how do you disable query wrapping on connection??
Thanks @jcoates 🙂
Lucky?? This is working for like an year....
And i tried to run more SP's of that database at DB Con v1 and all of them worked, so i believe that's not luck at all...
Disabling query wrapping on the connection at DB Con v2?? Or v1??
I believe that we didn't test, plan for, or support SPs in DB Connect version 1 or 2.