Anda di halaman 1dari 6

12/31/2015

AllAboutStoredProcedures|DatabaseAdministrationcontentfromSQLServerPro
IT/DevConnections

Store

Twitter
Facebook
Google+
LinkedIn
RSS
REGISTER LOGIN
SQLServerPro
SQLServer2014

SQLServer2012

SQLServer2008

Administration

Development

BusinessIntelligence

HOME > DATABASE ADMINISTRATION > ALL ABOUT STORED PROCEDURES

AllAboutStoredProcedures

SQLServerProCommunity

Creating,compiling,andusingstoredprocedures
MichaelD.Reilly|SQLServerPro
SHARE

Tweet

Oct21,2000
COMMENTS 5

AstoredprocedureiscompiledcodethatyoucancallfromwithinTSQLstatementsor
fromclientapplications.SQLServerrunsthecodeintheprocedureandthenreturnsthe
resultstothecallingapplication.Usingstoredproceduresisefficientforseveralreasons.
First,SQLServerhasalreadyparsed,optimized,andcompiledstoredprocedures,sothey
runquicklywithoutneedingtorepeatthesestepseachtime.Also,storedproceduresrun
ontheSQLServer,usingthepoweroftheserverandreducingtheloadontheclient
(whichmightbeamuchlesspowerfulcomputer).Finally,usingstoredprocedures
reducesnetworktraffic.InsteadoftheSQLServersendingallthedatatotheclientand
havingtheclientrunaquery,theclientsendsarequesttotheservertorunthe
procedure.Theserverreturnsonlytheresultdataset,whichisusuallyalotsmallerthan
thefulldataset.
Onceastoredprocedurehasrun,itremainsinmemory,sothenextusercanrunit
withoutincurringtheoverheadofloadingitintomemory.SQLServer6.5andearlier
releasesrequiremultiplecopiesoftheprocedureinmemoryifmorethanoneuserwillbe
runningtheprocedureatthesametime.SQLServer7.0improvedonthissituationby
lettingmultipleusers,eachwithadifferentexecutioncontext(includingparametersand
variables),shareonecopyoftheprocedureinmemory.

SignupfortheSQLServerProUPDATE
newsletter.

emailaddress
Country
Enteryouremailabovetoreceivemessagesabout
offeringsbyPenton,itsbrands,affiliatesand/orthird
partypartners,consistentwithPentonsPrivacyPolicy.

FromtheBlogs
ARTICLE

DEC8,2015

ItisTimetoMigrate
PowerBIforOffice
365 1
Don'tforgettomigrate
PowerBIforOffice365
contentbeforeyouleavefortheholidays.Deprecationof
PowerBIforOffice365startsattheendofDecember
2015.Hereiswhatyouneedtoknowtosuccessfully
moveyourbusinessintelligencecontenttothelatestand

Youcanusestoredprocedurestoenforcealevelofconsistencyinyourclientapplications.
Ifalltheclientapplicationsusethesamestoredprocedurestoupdatethedatabase,the
codebaseissmallerandeasiertomaintain,andyourunlessriskofdeadlocksbecause
everyoneisupdatingtablesinthesameorder.
Storedproceduresenhancesecurity,too,becauseyoucangivetheusersonlyEXECUTE
permissiononthestoredprocedures,whilerestrictingaccesstothetablesandnot
allowingtheusersanydirectupdateprivileges.Whenotherusersrunastoredprocedure,
theyrunitasiftheyhadthepermissionsoftheuserwhocreatedthequery.

greatestversionofMicrosoftPowerBI....More
NOV3,2015
SPONSORED

ClimbtheSteps
TowardDataQuality
Success
MelissaData'sData
QualityAnalystJosephVertidoexplainshowGartner
definesthecriticaldataqualitystepstopreventbaddata
fromenteringyoursystemsinthefirstplace,andthen

Youcandoalmostanythinginastoredprocedure,includingCREATEDEFAULT,
CREATEPROCEDURE,CREATERULE,CREATETRIGGER,andCREATEVIEW.You
cancreatetablesbothpermanentandtemporarybutanytemporaryobjectsyoucreate
withinastoredprocedurevanishwhenthestoredprocedureiscomplete.Andyoucan
neststoredproceduresupto32levelsdeep,sothatoneprocedurecancallanother,
whichcallsathird,andsoon.

keepitcleanovertime....More

Definitions

Properlyimplementedsecuritypoliciesalsoaccountfor

InSQLServerBooksOnline(BOL)andelsewhere,youmightseereferencestoseveral
typesofstoredprocedures,butthereareonlytwoprimarytypes.AstoredprocedureisT
SQLcodethatSQLServerhasparsed,optimized,andcompiled.Anextendedstored
procedureisaDLL(typicallywritteninCorC++)thatleveragestheintegrationofSQL
ServerandWindows2000/NTtomakeOSlevelcallsandperformfunctionsthatare
beyondTSQL'sscope.Bothtypescanacceptinputparametersandreturnoutputvalues,
errorcodes,andstatusmessages.Withinthetwoprimarytypesofstoredprocedure,you'll
findseveralothers.

organization....More

Localstoredprocedure:astandardstoredprocedure,executedonthelocalcomputer.
Youdefinestoredprocedureswithinadatabaseandtheybecomelocalobjectswithinthat
database.Youcancalllocalstoredproceduresfromanotherdatabasebygivingthefull
name,includingthedatabasename,ownername,andprocedurename.Youcanalsocall
themfromotherapplications,includingcommonclientapplicationssuchasMicrosoft

http://sqlmag.com/databaseadministration/allaboutstoredprocedures

BLOG

SEP29,2015

DataBreachesandInsiderThreats
IllsoundabitlikeCaptainObviousforbringingthisup,
butitsimportanttorememberthatsecurity
encompassesalotmorethanprotectingsensitivedata
fromthespecterofoutsiderthreatslikehackers.
threatmodelsthatincludeinsidersorpeoplewithinyour

SQLServerProForums
Getanswerstoquestions,
sharetips,andengagewith
theSQLServercommunityin
ourForums.

1/6

12/31/2015

AllAboutStoredProcedures|DatabaseAdministrationcontentfromSQLServerPro
AccessandVisualBasic(VB)applications.Typically,youusetheQueryAnalyzertocreate
localstoredprocedures.(YoucouldusetheEnterpriseManager,butitsnotveryhelpful
youstillhavetoknowhowtowritethecode,anditseasiertotestfromtheQuery
Analyzer.)
Temporarystoredprocedure:justlikealocalstoredprocedure,exceptthatthename
startswitha#symbolforaprivatetemporarystoredprocedureanda##foraglobal
temporarystoredprocedure.Aprivatetemporaryprocedureisgoodonlywithinthe
sessionitwascreatedinaglobalprocedurecanbeseenandrunfromothersessions.
Notethedifferenceinterminologybetweentemporarytablesandtemporaryprocedures.
Temporarytablescanbelocalorglobal,buta"local"storedprocedureisanyinthe
currentdatabase,soweusethewordprivatetodenotestoredproceduresthatarelimited
tothecurrentsession.
Remotestoredprocedures:astandardstoredprocedure,runonaremotecomputer.As
Einsteinmighthavepointedout,toanobserverontheremotecomputer,thisisactuallya
localstoredprocedurethathasbeenactivatedfromanothercomputer.Thestored
procedureexistsontheremotecomputeryoujustsendacrossthenetworkthesetof
instructionstorunit.InSQLServer7.0,distributedqueriesofficiallyreplacedremote
storedprocedures,buttheideasarethesameoneserverasksanothertorunastored
procedureandreturntheresultstothecallingserver.
Systemstoredprocedure:astoredprocedurethatyoucreateintheMasterdatabaseand
thatisavailabletoanyotherdatabase.Systemstoredprocedurenamesstartwithsp_the
term"systemstoredprocedures"isusuallyunderstoodtomeanthestoredprocedures
MicrosoftsupplieswithSQLServer.Youcancreateyourownsystemstoredprocedure
simplybycreatingastoredprocedureinMasterandprefixingitwithsp_.However,
Microsoftrecommendsthatyoudon'tusesp_whenyounameastoredprocedure.Ifyou
do,regardlessofwhereyoucreatedit,SQLServerlooksfirstinMaster,theninthe
databaseyouspecifiedinyourcallingstring,andfinally(ifyoudidn'tspecifyadatabase)
inthelocaldatabasewiththeDatabaseOwner(DBO)astheowner.Yes,SQLServerchecks
Masterfirst,evenifyousupplythedatabasename.Notonlyisthisinefficientifthe
procedureislocal,butaprocedurewiththesamenamemightexistinMaster,leadingto
confusion.

AnextendedstoredprocedureisaDLLthatiscodedinaprogramminglanguageother
thanTSQL.Anextendedstoredprocedure'snamebeginswithxp_.Microsoftsupplies
withSQLServersomeextendedstoredprocedures,suchasxp_readmail,whichhandles
readingemailmessagesonbehalfofthesp_processmailstoredprocedure.Oneespecially
versatileextendedstoredprocedureisxp_cmdshell,whichexecutesacommandstringas
anOScommandshell.(Essentially,youcanrunfromxp_cmdshellanycommandthat
youcanrunfromtheWin2K/NTcommandline.)
CreatingaStoredProcedure

Tocreateastoredprocedure,youmustbetheDBOorsystemsadministrator(sa),orbea
memberofthedb_ddladminrole.Userswiththepermissiontograntpermissionscan
grantotheruserspermissiontocreateproceduresusingTSQLcommands.Youcan't
grantthispermissiontospecificusersfromtheEnterpriseManagerinterfaceyouneedto
placetheminthedb_ddladminroleinstead.Whenyoucreatetheprocedure,youmust
havepermissiontoperformallthestepslistedinthequery.Thesestepsmightinclude
accessingothertablesorperforminginserts,updates,anddeletes.
Whenyoucreateaprocedure,youcancreateitonlyinthecurrentdatabase.Soyouneed
tospecifyonlytheprocedurename,notthedatabasenameoreventheownername.The
exceptiontothisruleistemporarystoredprocedures,whicharecreatedintempdb.
Procedurenamesmustbeuniquewithinadatabase,butyoucanusethesameprocedure
nameindifferentdatabases.Ifyouwantaproceduretobeavailableineverydatabasebut
don'twanttomakeitasystemstoredprocedureinMaster,addittotheModeldatabase.
Itwillappearineverynewdatabaseyoucreatethereafter.
Youcan'tcombinetheCREATEPROCEDUREstatementwithanyotherstatementinthe
samebatch.Thatrestrictionsoundsminoryoumightthinkthatyoucanjustputina
GOstatementandmoveontothenextpartofthescript.However,youcan'tputaGO
statementinthemiddleofaprocedure:AssoonasitreachesaGO,theparsertreatsthat
astheendoftheprocedureandcompileseverythinguptothatpoint.
Thesyntaxforcreatingastoredprocedureissimple:

CREATEPROCprocedure_name\[@parameterdatatype\]\[=default\]\[OUPUT\],\[@param

Youspecifyinputparametersas@parameter_name,andyoumustdefineadatatypefor
eachparameter.Optionally,youcanspecifyadefaultvalueforanyparametersthe
defaultmustbeaconstantorNULL.Procedurescancontainupto1024parameters
thesearelocaltotheproceduresoyoucanusethesameparameternamesforother

http://sqlmag.com/databaseadministration/allaboutstoredprocedures

2/6

12/31/2015

AllAboutStoredProcedures|DatabaseAdministrationcontentfromSQLServerPro
procedureswithoutriskofinterference.Ifyouwantaparametertoreturnavalue,you
mustspecifytheparameterasanOUTPUTparameterwhenyoucreatetheprocedure.
Youdon'tnecessarilyalwayshavetoaskfortheparameterasareturnedparameter,but
unlessyouhavedefineditasapotentialoutputparameter,youcan'taskforaparameter
toreturnavaluewhenyouexecutetheprocedure.Parameterscanactasbothinputand
outputparameters,soasimpleprocedurecouldhaveonlyoneinputparameter,withthe
valuebeingmodifiedandpassedbackasanoutputparameter.
TheWITHENCRYPTIONoptionpreventsothersfromreverseengineeringyour
proceduresbylookingatthecodeinthesyscommentstable.Italsopreventsyoufrom
lookingatthecodebecausethereisnowaytoaskforthecodetobeunencrypted.SQL
Servercanunencryptit,becauseitcanrecompilethecodewhennecessary,including
whenyouupgradetoanewreleaseofSQLServer.Butyoucan'tsupplyakeyorpassword
tounencryptthecode,sokeepacopyofyoursourcecodesomewheresecure.
Ifyouneedtochangethedefinitionofastoredprocedure,youcandosobyrerunning
theCREATEPROCEDUREstatement,changingCREATEPROCEDUREtoALTER
PROCEDURE.SQLServer7.0introducedtheabilitytoALTERdatabaseobjects,soyou
canchangeobjectswithouthavingtodropandrecreatethemasyouhadtodoin
previousreleases.Droppingtheobjectalsoremovesallpermissionsonthatobject,so
whenyourecreateadroppedobject,youalsohavetorebuildthepermissions.(Scripting
thepermissionsonanobjectbeforeyoudropitisalwaysagoodidea.)
TheCreationProcess

Whenyoucreateastoredprocedure,SQLServerplacesanentryinthesysobjectstablefor
thedatabase,listingthenewobject.SQLServerparsestheTSQLcodeandchecksitfor
syntaxerrors,thenstorestheprocedurecodeinthesyscommentstable(initsencrypted
form,ifyouchosethatoption).AprocesscalledDelayedNameResolutionletsyoucreate
storedproceduresandrefertoobjects,suchastables,thatdon'tyetexist.Theparser
doesn'tgiveyouanerrorbecauseitassumesthattheobjectreferencedwillexistbythe
timeyouexecutethequery.
RunningaProcedurefortheFirstTime

Whenyouexecutestoredprocedureforthefirsttime,thequeryoptimizerbuildsan
executionplanfortheprocedure,thencompilestheplanandusesittorunthe
procedure.SQLServer2000and7.0don'tstorethisexecutionplanpermanently.The
planremainsinmemoryunlessyourrecompileoptionsspecifyotherwise.Theprocedure
cacheisanareaofmemorywhereSQLServerkeepsstoredproceduresandcached
queries.SQLServer6.5andearlierreleasesrequiredyoutoconfigurehowmuchofthe
availablememorytoallocatetodatacacheandhowmuchtoprocedurecache.SQL
Server2000and7.0allocatethememorydynamicallytoeachcacheasSQLServer
requires.
RunningtheProcedureAgain

Oncetheprocedureisinmemory,otherclientapplicationscanuseitwithoutanyaction
ontheirparttheysimplyruntheprocedure,andifitisfoundinmemory,theyuseit.If
theprocedureisn'tinmemory,SQLServermustreoptimizeandcompileit.MostSQL
Serverswithadequatememorykeepfrequentlyrunproceduresinthecache.Butif
memoryusebecomesaconcern,SQLServercandropsomeproceduresfrommemory.It
usesasophisticatedalgorithmtodecidewhichtodropandwhichtokeep,giving
preferencetothemostfrequentlyusedprocedures,buttakingintoaccounttheeffort
necessarytorecompileaprocedureifitwereflushedfromthecache.Inotherwords,the
algorithmcalculateswhethertodroponelargeprocedurethathasn'tbeenusedforalong
time,orseveralsmallproceduresthatareusedoccasionallybutnotfrequently.
Userscanshareacopyoftheprocedureinmemoryaslongastheirenvironmentthe
server,database,andconnectionsettingsisidentical.Differentconnectionsettings
requiredifferentcopiesoftheprocedureinmemory,sotrytostandardizeconnection
settings(SEToptionssuchasANSIPADDING,forexample).Andhere'saheadsupfor
databasedesigners:Userscan'tshareacopyofaprocedureifareferencedobjectrequires
nameresolution.Suchasituationcanoccurwhentwoobjectshavethesamenamebut
differentowners:forexample,thesalesandengineeringdepartmentsmighteachhave
addedatablecalled"budget,"withdifferentowners.Oraprogrammermighthavemade
acopyoftheemployeestable,andownthecopybutnottheoriginal.Havingrulesin
placeaboutobjectnamingandownershipideallyallobjectshaveuniquenamesandare
ownedbytheDBOwillpreventthisproblem.

http://sqlmag.com/databaseadministration/allaboutstoredprocedures

3/6

12/31/2015

AllAboutStoredProcedures|DatabaseAdministrationcontentfromSQLServerPro
RecompileOptions

Onebenefitofstoredproceduresisthattheyremaininmemoryandcanbereuseduntil
theserverisrestarted,sotheycouldbeinmemoryformonths.Insomesituations,you'll
wanttorecompileaprocedure.Forexample,youmighthaveaprocedurethatproduces
radicallydifferingresultseverytimeyourunit,suchasaproceduretoreturnalistof
customernamesandaddressesforarangeofZIPcodes.Ifyourunthisprocedureona
fewZIPcodesinNewYork,youmightgetbackseveralthousandnames.Butifyourunit
onalargerrangeofZIPcodesinWyoming,youmightgetonlytwoorthreenames.For
suchastoredprocedure,considerputtingthekeywordsWITHRECOMPILEinthe
CREATEPROCcode.SQLServerwillthendiscardthecompiledexecutionplanevery
timetheprocedureisrun,andrecompileitagainforthenextuser.
Youmightusuallyrunastoredprocedurewithcertainparametersforexample,ifmost
ofyourbusinessisinNewYork,youexpectalargenumberofnamesperZIPcode.When
youneedtosendamailingtoWyoming,youcanrunthequeryagain,usingthe
EXECUTEprocnameWITHRECOMPILEoption.SQLServerdiscardstheplaninthe
procedurecacheandcompilesanewonewiththeatypicalparameters,soyourprocedure
runswiththequeryoptimizedforthismailinglist.Asacourtesytothenextuser,you
shouldrunthequeryagain,usingatypicaldatasetandtheWITHRECOMPILEoption.
Ifyoudon't,youratypicalplanwillsitinmemory,andthenexttimesomeonerunsthe
procedure,SQLServerwilluseit.
Youmightalsoconsiderrecompilingyourprocedureifyouaddanindextothetable.
Recompilinggivesthequeryoptimizerachancetocalculatewhetherthenewindexmight
beuseful.Thecommandtousehereissp_recompile.Youcanspecifyaprocedurename
fortherecompile,oryoucansupplyatablenameorviewname.Ifyouspecifyatableor
view,SQLServerwillrecompileallproceduresthatreferencethattableorviewthenext
timetheyrun.
AutomaticRecompile

BOLsaysthat"SQLServerautomaticallyrecompilesstoredproceduresandtriggerswhen
itisadvantageoustodoso."Actually,allSQLServerdoesiskicktheprocedureoutofthe
cache,soithastorecompiletheprocedurethenexttimeitruns.SQLServerrecomputes
thestatisticsonanindexwhentherehavebeenasignificantnumberofchangestothe
data.Withnewstatistics,recompiling(andthereforereoptimizing)thequerymakes
sense.Ifyoudropanindexthataprocedureused,theprocedurewillneedrecompiling.
Anytimeyourebuildindexestoreclaimspaceinthedatabase,SQLServerrecompilesthe
procedurewiththenewindexstatistics.Soit'sunlikelythatanyprocedurewillremainin
memoryindefinitely.Infact,bynotstoringoptimizedqueryplans,SQLServer2000and
7.0lookforopportunitiestorecompilewiththelateststatistics.
TemporaryStoredProceduresvs.CachedQueries

AsImentioned,youcancreateatemporarystoredprocedurebystartingtheprocedure
namewith#or##,andtheseproceduresarebuiltintempdb.Aprivateprocedurecanbe
usedonlyinthesessionwhereitwascreatedaglobalprocedurecanbeusedbyanyone
withtherightpermissions,butitvanisheswhenthesessionitwascreatedinis
disconnected.Fortunately,SQLServerletsanyonerunningtheprocedureatthetime
completetheprocedure.Also,ifyoucreatestoredproceduresintempdbdirectly,you
don'tneedtostartthenamewith#or##.Youjustrunthefollowingcommandfrom
yourdatabase
EXECUTEtempdb.dbo.procname

andthestoredprocedureremainsintempdbuntiltheserverrestarts,evenifyoulogoff.
Ifyoudon'twanttocreatetemporarystoredproceduresintempdb,youcancreatethe
procedureinyourdatabase,useit,thendropit.
SQLServer2000and7.0cancachequeries,soSQLServercanspotaquerybeing
repeated.Itcanalsodetectaquerybeingrunoverandoverwithjustonedifferent
parametersaysomeoneinsalesiscallingupcustomerdataandtheonlydifferencein
eachiterationisthecustomerID.SQLServercantakethisquery,treatcustomerIDasa
parameter,andusethesameexecutionplanwithdifferentcustomerIDvalues.Thatway,
SQLServeravoidshavingtoparse,optimize,andcompileeverytime.(Thisprocessis
sometimescalledautoparameterization.)Youalsohavetheoptionofusingthe
sp_executesqlsystemstoredproceduretotellSQLServerthatyou'regoingtokeep
sendingitthesamequerywithdifferentvalues.Thisoptionisgreatifyouhavealoopin
yourcodeanduseittostepthroughalistofupdatestoatableoneatatime.

http://sqlmag.com/databaseadministration/allaboutstoredprocedures

4/6

12/31/2015

AllAboutStoredProcedures|DatabaseAdministrationcontentfromSQLServerPro
SoifSQLServercancachequeriesanddiscardthemwhenitisdonewiththem,what's
thedifferencebetweenatemporarystoredprocedureandacachedquery?Notalot,
really.Bothareparsed,optimized,compiled,used,anddropped.Thebiggestdifferenceis
thatthecachedqueryusesspaceinyourdatabase,andthetemporaryprocedureisbuilt
intempdb.Thatdistinctionmightbenotbeimportantunlessyou'reworkingonaserver
withmanyotheruserswhoarecompetingforspaceintempdb.Microsoftrecommends
thesp_executesqlapproach,andIagreebecauseofthereducedpossibilityofcontention
intempdb.
AutomaticStoredProcedureExecution

SQLServerhasalittleknownfeaturecalledautomaticstoredprocedureexecution,which
letsyouspecifystoredprocedurestorunwhentheserverstartsit'slikeanautoexec.bat
fileforSQLServer.Tomakeaprocedurerunatstartup,runthesp_procoption
procedurewiththesyntax
sp_procoptionprocnamestartuptrue

Youcanusetrueorontomaketheprocedurerunatstartupandfalseorofftoremoveit
fromthelistofprocedurestorunatstartup.(InSQLServer6.5,yourunsp_makestartup
andsp_unmakestartuptoaddprocedurestoorremovethemfromtheautostartlist.
Theseproceduresdon'texistinlaterreleases.)Becarefulaboutaddingmultiple
proceduresbecausealltheprocedureswillstartatonce.Ifyouneedtheproceduresto
runinasequence,buildoneprocedurethatcallsalltheothersintherightorder,then
makethatoneanautostartprocedure.
StoredProcedureGuidelines

Youmightprefertouseaprefixofusp_foruserstoredprocedures,butthere'sno
acceptedindustrywidenamingstandard.Microsoftrecommendslimitingeachstored
proceduretoexecutingonetask.Ifyouneedtoperformmultipletasks,youcancreate
oneprocedurethatcallsalltheothersinthecorrectsequence.Ifyou'veusedthetasksin
thesequenceelsewhere,modularizingthecodemakessense.Butthere'snoreasonnotto
haveasequenceoftasksinoneprocedure.Youmightencounterproblems,though,ifyou
buildbranchinglogicintotheprocedureorifyouhaveaprocedurethatperformsoneof
severaldifferenttasksdependingontheinputparameters.Ifyouruntheprocedurethe
firsttimewithasetofparametersthatcauseittoactivatebranchB,SQLServercan't
optimizethecodeforbranchesAandC.Andifyouusebranchinglogic,youloadinto
memorycodethatyoumightnotuseveryoften.Soforastraightthroughsequencethat
SQLServerprocessesfromstarttofinish,youmightbebetteroffwritingitwithmore
stepsinfewerprocedures.Forbranchinglogic,havingeachbranchasaseparate
procedureandcallingthemasneededmightmakemoresense.
GroupingStoredProcedures

Groupingstoredproceduresisoneofthosefeaturesthatnobodyseemstouse,which
makesitalikelyexamtopic.Ifyouhaveseveralassociatedprocedures,perhapsforthe
branchinglogicIdiscussed,youcangroupthembynamingthemwiththesamename
andindividualidentificationnumbers,withasemicolonbetweenthenameandthe
number.Theprocedurenameswouldlooklikeprocname1,procname2,andsoon.The
benefitofusingthisnamingconvention,apartfromconsistency,isthatyoucanusea
DROPPROCEDUREprocnamecommandtodropalltheproceduresatonce.However,
afteryougrouptheprocedures,youcan'tdropthemindividually.
StoredproceduresareapowerfulpartofSQLServer.Theyofferbenefitsinbothsecurity
andperformance.Anyclientapplicationyouusewillalmostcertainlyrunbetterifyou
addsomestoredproceduresrunningontheserver.

SHARE
PRINT

REPRINTS

Tweet

FAVORITE EMAIL

DiscussthisArticle

onMay25,2005

AnonymousUser(notverified)

GoodArticle.............
LogInorRegistertopostcomments

AnonymousUser(notverified)

http://sqlmag.com/databaseadministration/allaboutstoredprocedures

onMay24,2005

5/6

12/31/2015

AllAboutStoredProcedures|DatabaseAdministrationcontentfromSQLServerPro
sdf
LogInorRegistertopostcomments

onAug2,2005

AnonymousUser(notverified)

itisgoodarticalandcoveritssubjecttopic.
LogInorRegistertopostcomments

onJul10,2005

AnonymousUser(notverified)

Greatjob!Youalmostcoveredeverything.
LogInorRegistertopostcomments

onOct14,2014

olia

greatarticle,appreciateit.manythanks.
LogInorRegistertopostcomments

PleaseLogInorRegistertopostcomments.

Related Articles
JumpStart:InsideStoredProcedureTemplates
AllAboutRAISERROR

AdditionalFactsAboutConfiguringTransactionalReplication
GetWiseAboutBits

LearningAboutOLEAutomationStoredProcedures30Dec1999

SQLMag.com
Home SQLServer2012 SQLServer2008 SQLServer2005 Administration Development BusinessIntelligence

Site Features

Penton

About

PrivacyPolicy

Awards

TermsofService

CommunitySponsors

Advertise

MediaCenter

Follow Us

RSS

Search SQLMag.com

Sitemap
SiteArchive
ViewMobileSite

Related Sites
DevPro SharePointPro WindowsITPro SuperSiteforWindows IT/DevConnections myITforum

Copyright2015Penton

http://sqlmag.com/databaseadministration/allaboutstoredprocedures

6/6

Anda mungkin juga menyukai