I made a oledb connection to a SQLServer 2014 database. When I create a SQL task, calling a procedure, the menu lists all procedures with ';1' or ';0' behind their names. The parameters are shown correctly. However, when the taks runs, the procedure isn't called. When I manually remove the ';1' from the procedure name, the procedure runs, but the parameters must be added manually.

What am I doing wrong? Can't I use oledb for this?

I just tested and I got the same result as you. Definitely looks like a bug. Apart from that, why don't you use the mssql connection method instead of oledb?


thomas

Sorry for the late reply. I switched to mssql and it works now. I had no particular reason to use OLEDB.

We will look at this for ODBC/OLEDB. Thanks for the report!

---

This has now been fixed for version 8.1.1 even though we found that you need to call it with ;1. We have just made this transparent.

---

Great, thanks! I'm always amazed at how quickly things get fixed/updated at Visualcron.

Great, thanks! I'm always amazed at how quickly things get fixed/updated at Visualcron.

Yes me also 😁