Feature: Drop/Create for stored procedure synchronization

csuire

Add new Project Behavior:
"Do not use ALTER to modify stored procedures or views"

Description:
When this option is selected, SQL Compare will drop and then create any stored procedures and views that are to be synchronized rather than using the ALTER method. This will create the "if exists() drop..." sql code even if the stored procedure is being added for the first time.

Example Output:
This is similar to scripting stored procedures from Enterprise manager.

if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[ExampleStoredProcedure]') and OBJECTPROPERTY(id, N'IsProcedure') = 1)
drop procedure [dbo].[ExampleStoredProcedure]
GO

CREATE PROCEDURE [dbo].[ExampleStoredProcedure] ...


Please note that this feature request is similar to this previous post:
http://www.red-gate.com/messageboard/vi ... t=2747#top

Thanks!

Michelle T

I've added this forum thread to the feature request covering this behaviour.

jhogan

I second...
We need this feature because we can make only a limited number of assumptions about the target databases. We can't assume that procs will exists. ALTER's have caused scripts to fail for us in the past because the proc didn't exist.

Is there anyway I can check the status of this feature request?

David Atkinson

We're looking closely at feature and actively looking for user requirements in this area. If there are any more examples of what you'd want the generated script to look like if we added a "Make scripts rerunnable" option, please let us know what they are. Is it only ever Stored Procedures that may already exist on the target server, or are there other objects or object properties that you need to check for existence?

David Atkinson
Product Manager
Red Gate Software

David Atkinson

We have options for rerunnable scripts in the latest Beta.

would you be able to let us know if this meets your requirements?

http://www.red-gate.com/MessageBoard/vi ... hp?t=14113

Kind regards,

David