We help IT Professionals succeed at work.

Whether Drop and Create Stored Procedure is best practice for deployment (or) Alter Stored Procedure is best practice for deployment?

99 Views
Last Modified: 2019-01-24
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?
Comment
Watch Question

Pratik SomaiyaApplication Development Analyst
CERTIFIED EXPERT

Commented:
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 SomaiyaApplication Development Analyst
CERTIFIED EXPERT

Commented:
whenever you DROP and CREATE you may lose the permissions associated with that object.
CERTIFIED EXPERT

Commented:
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?
chokkaStudent

Author

Commented:
@SStory, My question is " Which is the best practice? "

Either Drop and Create
(or)
Alter


I understand about losing the permission on Drop and Create. We can add a Grant Permission syntax after create.

  1. Drop Procedure
  2. Create Procedure
  3. Grant Permission


Which is the best practice to follow for SP Deployment from DBA Stand point?
Database Developer
Commented:
This problem has been solved!
(Unlock this solution with a 7-day Free Trial)
UNLOCK SOLUTION
chokkaStudent

Author

Commented:
Thanks
Doug BishopDatabase Developer

Commented:
no problem. Thank you.