Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Default Values and Named Parameters for Stored Procs Expand / Collapse
Author
Message
Posted Friday, December 20, 2002 12:00 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: Moderators
Last Login: Today @ 7:39 AM
Points: 6,705, Visits: 1,677
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/awarren/defaultvaluesandnamedparametersforstoredprocs.asp>http://www.sqlservercentral.com/columnists/awarren/defaultvaluesandnamedparametersforstoredprocs.asp

Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter
Post #8948
Posted Wednesday, January 08, 2003 4:17 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Sunday, August 31, 2008 12:56 PM
Points: 281, Visits: 2
I would say it is always nice to have a default behaviour for a stored proc.
If you dont give it any parameters it will perform the default behaviour.

But when you need a different behaviour you could call the sproc with a parameter.

I don't see anything wrong with this......

If anybody could tell me why this is wrong I could learn from them.





Post #50170
Posted Wednesday, January 08, 2003 4:51 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, May 01, 2013 8:12 AM
Points: 1,104, Visits: 331
I like default parameters to specify default behaviour. If a default value needs to change (customer requirement etc..) this change only has to be made in one place, whereas if you hadn't used a default this change would have to be made in every calling piece of code, maybe in multiple applications.

Regards,
Andy Jones



Regards,
Andy Jones
Post #50171
Posted Wednesday, January 08, 2003 6:08 AM
SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: Moderators
Last Login: Wednesday, March 26, 2014 3:38 PM
Points: 8,369, Visits: 732
I like them primarily when I may have a value that can be NULL just so that all the parameters do not need to be expressed. But to make usefull to most folks you need to put defaulted values toward the end otherwise they in some cases end up doing more work than needed.

Ex.

CREATE PROC ip_test

@val1 as varchar(4) = NULL,
@val2 as varchar(4) = NULL

nw I want to set @val2 to TEST and leave @val1 out

ip_test @val2 = 'TEST'
ip_test NULL, 'TEST'

So there you see the value list was shorter to code than having to specify @val2. This sometimes can be a drawback if you use highly desciptive variable names one small data values. It is just a nicity that you have the option.

However in the example if I wanted to set @val1 to TEST then I would do

ip_test 'TEST'

which is short than the other two. My opinion is supply all values up to the last item you need and anything that can be defaulted put at the end of you list of inputs. Thus making it of the most possible use.




Post #50172
Posted Wednesday, January 08, 2003 10:05 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Saturday, February 24, 2007 4:37 PM
Points: 322, Visits: 1
I find default parameters very useful as I work in an environment where I often have an Access application sharing an SPROC with a web page where a parameter might be needed for the web page but is always the same coming from the application.

Patrick Edgerton
DBA Resource Concepts




Post #50173
Posted Wednesday, January 08, 2003 11:20 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: Moderators
Last Login: Today @ 7:39 AM
Points: 6,705, Visits: 1,677
Thanks for your comments so far!

Andy
http://www.sqlservercentral.com/columnists/awarren/




Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter
Post #50174
Posted Wednesday, January 08, 2003 11:43 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, June 30, 2004 8:52 AM
Points: 253, Visits: 1
Just one little drawback of using default values for SP parameters...

Think of default values as you think of late binding in programming languages. If you forgot to specify a parameter for your SP, it won't give you a compile-time error. Instead it will run as if everything is fine. Even if you put an appropriate parameter validation in the beginning of SP, you will see it only at execution time, not at compile time.




Post #50175
Posted Wednesday, January 08, 2003 12:02 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, July 17, 2012 9:43 AM
Points: 164, Visits: 29
I find default parameters to be very useful when a single stored proc is being used by multiple versions of client software (ie-web, client/server). If one of the applications supports additional functionality and parameters, then it can be implmented with no code changes to the legacy applications.

-Dan



-Dan
Post #50176
Posted Friday, July 09, 2004 4:15 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Saturday, January 05, 2013 10:33 PM
Points: 2, Visits: 16

Tinkering with stored procedure parameters

Theoretically what i did is to make the procedures behave as if they do not have parameters when no parameter is passed to the procedure when it is called. This equivalent of passing a null to the procedure parameter...

Therefore if you call the procedure with no parameters the procedure will return all values...you will then only need to specify values for the parameters you need.

To achieve this instead of specifying your parameter as say:-

...WHERE CustomerID=@CustomerID specifiy

....WHERE CustomerID=COALESCE(@CustomerID,CustomerID)

With fine tuning you will find great potential of using stored procedure...

Contact me at clarence_assey@hotmail.com for more help

Post #125603
Posted Wednesday, July 02, 2008 7:30 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, July 02, 2008 7:27 AM
Points: 1, Visits: 2
Actually last week i coded my application with a parameter refresh. but i think this is more handy... ok now im going to go back and check whether my asp application can pass the parameters as u have mentioned. if its works... Thank you Maan...
Post #527309
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse