Adding a migration after a manual change to production

• 
  Hi,
  
  Are you using a SQL Source Control or a SQL Change Automation project?
  
  Kind Regards,

  Sergio R January 20, 2020 15:08

  - 0 +
• 
  It's a SQL Change Automation project.

  asadc January 21, 2020 12:26

  - 0 +
• 
  Assuming that you are using the default option of using Programmable Objects, then it's just a case of adding the Stored Procedure to your development database and importing it.
  This will generate a Programmable Objects script that will be deployed in Production and will drop the existing Stored Procedure and recreate it.

  Sergio R January 23, 2020 11:50

  - 0 +
• 
  We're not using programmable objects, so the script that's generated will be a CREATE. I ended up manually modifying the generated script by adding a DROP, I'm not sure if there's a better way. =

  asadc January 24, 2020 09:43

  - 0 +
• 
  We would advise using the same approach used in Programmable Objects, drop the the object if exists and then script the CREATE:
  
  For example:
  

  
  IF OBJECT_ID('[HumanResources].[uspUpdateEmployeeHireInfo]') IS NOT NULL

  DROP PROCEDURE [HumanResources].[uspUpdateEmployeeHireInfo];

  
  

  Sergio R January 28, 2020 20:06

  - 0 +

Add comment

Please sign in to leave a comment.