How to make input parameters mandatory in Stored Procedure ?

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » SQL Server 2005 General Discussion » How to make input parameters mandatory in...

How to make input parameters mandatory in Stored Procedure ?

Rate Topic

Display Mode

Topic Options

Author

Message

anjali.vishwakarma

Posted Thursday, August 28, 2008 7:24 AM

Valued Member

Group: General Forum Members
Last Login: Friday, September 16, 2011 3:37 AM
Points: 54, Visits: 148

When we create a Stored Procedure , how can we define input parameters mandatory ? For eg.

create procedure ProcTest1
@policy_id int,
@policy_name varchar(100),
begin
end

When i execute this SP, if I dont pass any value for these 2 parameters, it gives error that Procedure expects these 2 parameters.
But when i execute this procedure and select checkbox for 'Pass Null Value' against these 2 parameters, it executes well without showing message.

How can I make it mandatory so that NULL is not allowed for these 2 parameters ?

Post #560409

Jack Corbett

Posted Thursday, August 28, 2008 7:39 AM

SSChampion

Group: General Forum Members
Last Login: Today @ 1:41 PM
Points: 10,613, Visits: 11,952

There is no way in SQL Server to enforce that a non-null value is passed to parameter. You would need to verify the values within the stored procedure or the client application.

Jack Corbett

Applications Developer

Don't let the good be the enemy of the best. -- Paul Fleming

Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
How to Post Performance Problems
Crosstabs and Pivots or How to turn rows into columns Part 1
Crosstabs and Pivots or How to turn rows into columns Part 2

Post #560433

GSquared

Posted Thursday, August 28, 2008 7:43 AM

SSCoach

Group: General Forum Members
Last Login: Yesterday @ 1:45 PM
Points: 15,442, Visits: 9,572

You can't actually make them mandatory, but you can add something like:

create proc MyProc
(@MyParam1_in datatype)
as
if @MyParam1_in is null
  raiserror('Null values not allowed for MyParam1_in', 16, 1)

...the rest of the proc...

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

Post #560442

anjali.vishwakarma

Posted Friday, August 29, 2008 4:12 AM

Valued Member

Group: General Forum Members
Last Login: Friday, September 16, 2011 3:37 AM
Points: 54, Visits: 148

Thanks to All.

Post #561084

john_jakob

Posted Friday, August 29, 2008 4:16 PM

Grasshopper

Group: General Forum Members
Last Login: Thursday, February 21, 2013 11:46 AM
Points: 19, Visits: 100

I often use parameter validation in the proc -- ALONG WITH default parameter values on the proc --e.g.,

CREATE PROC spMyProc
@State CHAR(2) = 'CA',
@Country VARCHAR(32) = NULL
AS
BEGIN

-- Disallow NULL Country!
IF (@Country IS NULL)
SET @Country = 'USA'

. . .

END
GO

Here the user can pass either 0, 1, or 2 parameters, and things should still work.

Post #561557

« Prev Topic | Next Topic »

Permissions