Comments on: Optional parameters in Stored Procedure

By: Mehboob Ali Yousafzai

Mehboob Ali Yousafzai — Thu, 14 Oct 2010 14:46:48 +0000

Sir,if suppose i had a store procedure to insert two fields in a table,
Create procedure test
@a int =null,
@b nvarchar(50) =null
as
insert into tblName(col1,col2)
values(@a,@b)
go

Now when i execute the following line it successfull
exec test
& also
exec test 1,’Swabi’
But if i only want to insert nvarchar(50) data i.e in @b(col2),then what should i do?
exec test ‘Swabi’ –error,as first argument is integer missing…

Can any one help me plz !!!

By: linglom

linglom — Wed, 20 May 2009 09:51:16 +0000

Hi, Jonathan
Specify parameter name can solve your problem.

For example,
EXEC [dbo].[sp_getproduct] @UnitsInStock = 20
exec usp_StoredProcA param1 = 10, param3 = 20

By: Jonathan

Jonathan — Wed, 20 May 2009 08:48:46 +0000

Hi,
I’m having problms using optionals. I’m using 3 params in my stored proc. Param 1 is required but params 2 and 3 are optionals. I can run my stored proc fine if I omit both params 2 and 3. But if I omit param 2 and pass a value to param 3, SQL Server complains:
Msg 102, Level 15, State 1, Line 1
Incorrect syntax near ‘,’.

The syntax I used is:
exec usp_StoredProcA param1,, param3

If I do the following:
exec usp_StoredProcA param1, ”, param3

param 2 is interpreted as empty string and not the default value that I specified.

Sorry for the long email. Hope I explained myself clearly.

By: linglom

linglom — Tue, 12 May 2009 02:34:47 +0000

Hi, Priya
The example above is to execute the store procedure without specify parameters by set default values (NULL) to the parameters.

By: Priya

Priya — Thu, 07 May 2009 09:52:57 +0000

I cant understand with this example