Posted by CK on 10/02/75 11:50

Hi All,
Quick question, I have always heard it best practice to check for exist, if
so, drop, then create the proc. I just wanted to know why that's a best
practice. I am trying to put that theory in place at my work, but they are
asking for a good reason to do this before actually implementing. All I
could think of was that so when you're creating a proc you won't get an
error if the procedure already exists, but doesn't it also have to do with
Compilation and perhaps Execution. Does anyone have a good argument for
doing stored procs this way? All feedback is appreciated.
TIA,
~CK

• Next in forum: Re: output the latest date for each foreign key
• Prev in forum: Copy text columns to nvarchar
• Thread view: Stored Proc Question : Why If Exisits...Drop...Create Proc?

[Reply to this message]