Quote Originally Posted by Martin Moleman View Post
Passing varchar(max) as a parameter to a stored procedure was actually fixed a long time ago, but we forgot to also handle it for nvarchar(max).
The latest 19.1 build (A5) has this fixed for nvarchar(max) as well.
Thanks Martin. Good to know it's fixed when we move to 19.1.

Quote Originally Posted by Martin Moleman View Post
Named parameters are currently not possible. This is relatively new (SQL 2016) and only for stored procedure parameters. I made a note to see if we can support this.
Yes please.

Quote Originally Posted by Martin Moleman View Post
Wow, that's a lot of parameters. This would only be possible with named parameters. You could probably create your own 'in-between' stored procedure that takes 8 parameters that then calls the actual stored procedure with named parameters.
Yes it is quite a lot. For now I have set each one.

If anyone is interested in a sample workspace using this stored proc. I am happy to post it.