Stored procedure default parameter value null

Tableau Community Tableau asked a question. I have a sheet with a Procedure as a dataset. This procedure has a parameter that is a string type and the procedure definition defaults to NULL. However, when called from tableau, if the parameter is left empty, the procedure is called with an empty string rather than NULL.

What is the goal here? If you're looking to just connect to a Stored Procedure, without any parameters, you can do so by not setting a parameter value at all, and leaving it blank while connecting. We did this for a short time. When I use a Param filter control and I leave the field blank, it sends an empty string. Set that as your dataset in a tableau ws then create a parameter filter control from the param. See what I mean? No, I don't. When I ask about the "goal", I mean what are you hoping to accomplish in Tableau by doing this?

Because the state you pass into the dataset SP is used by Sp logic to decide what to return to tableau. I can easly change the SP to use empty string instead of null, but, isn't the fact that tableau can't handle nulls in this scenario, a deficiency?

I really don't know what you're trying to accomplish--you can share your concerns with support tableausoftware. Matt Lutton. The use case for this and it's a common thing in SQL is to have a parameter that can filter in the SP by the parameter while also returning unfiltered data when the parameter is not passed, or a null is explicitly passed in..

This is a standard pattern for sql stored procedures in common use everywhere and Tableau doesn't appear to work with stored procedures designed this way. By: Greg Robidoux Overview The real power of stored procedures is the ability to pass parameters and have the stored procedure handle the differing requests that are made. Explanation Just like you have the ability to use parameters with your SQL code you can also setup your stored procedures to accept one or more parameter values.

Address GO. EXEC dbo. Back To Top I really enjoyed going through this nice tutorial. I really appreciate your great work. Also remember two interesting facts about stored procedure parameters: 1. When you execute the stored procedure, you don't NEED to outline the names of the parameters. As long as you outline parameter names when you execute your SP, the order of your parameters can be in any way you want. The parameter names and values don't need to be in the same order they are defined in the SP!

It was very helpful. It would be great if the execution is also showed. Hi Will, there is not any real purpose to have a prefix for any of the objects. Learn more. Asked 13 years, 3 months ago. Active 13 years, 3 months ago. Viewed 8k times. I'm a newbie when it comes to SQL. I have tried to use NULL instead of ''.

When calling it like this: cmd. Parameters[" description"]. Description; result. Here's the calling command: cmd. Add " description", SqlDbType. VarChar ; cmd. Add " message", SqlDbType. Parameters[" name"]. Name; cmd. Open ; cmd. MrValdez 8, 10 10 gold badges 52 52 silver badges 78 78 bronze badges. Adam Driscoll Adam Driscoll 9, 7 7 gold badges 58 58 silver badges bronze badges. Add a comment. Active Oldest Votes.