Whether Drop and Create Stored Procedure is best practice for deployment (or) Alter Stored Procedure is best practice for deployment?
Whether Drop and Create Stored Procedure is best practice for deployment (or) Alter Stored Procedure is best practice for deployment?
I am working on automating a process of deploying Stored Procedures across the Servers through SSIS Package.
My clarification is, when we deploy an existing stored procedure across the environments , Whether we can drop and create (or) Alter would be fine?
Microsoft SQL ServerSSISSQL
Last Comment
D B
8/22/2022 - Mon
Pratik Somaiya
Ohh okay, I got your question now.
You should use ALTER in case of the stored procedure so as to maintain the permissions associated with that stored procedure.
Regards,
Pratik
Pratik Somaiya
whenever you DROP and CREATE you may lose the permissions associated with that object.
SStory
I haven't used SSIS. I am curious though as to why you wouldn't drop if exists and the recreate them. Are you worried about losing permissions on them? If so can't it run something to GRANT those as needed?
You should use ALTER in case of the stored procedure so as to maintain the permissions associated with that stored procedure.
Regards,
Pratik