configuration for "modeling" the scripts

Hello

What I need is a configuration with which I can determine how the script should look like.

For example:
I'd like to have:

IF NOT EXISTS 
    &#40;SELECT * FROM sys.objects WHERE OBJECT_ID = OBJECT_ID&#40;N'&#91;&lt;SchemaName,,&gt;&#93;.&#91;&lt;SPName,,&gt;&#93;'&#41;AND TYPE IN &#40;N'P', N'PC'&#41;&#41;
    EXEC sp_executesql N'CREATE PROCEDURE &#91;&lt;SchemaName,,&gt;&#93;.&#91;&lt;SPName,,&gt;&#93; 
    AS 
    BEGIN 
        SET NOCOUNT ON;
    END'
GO

ALTER PROCEDURE &#91;&lt;SchemaName,,&gt;&#93;.&#91;&lt;SPName,,&gt;&#93;
-- parameterlist
AS
    --stored procedure code
GO

instead of:

CREATE PROCEDURE &#91;&lt;SchemaName,,&gt;&#93;.&#91;&lt;SPName,,&gt;&#93; 
-- parameterlist
AS 
    BEGIN 
       --stored procedure code
    END
GO

I need this for all "code objects" like stored procedures, functions, etc.
The reason is first, with drop/create some dependencies are lost. And second, I already have missing dependencies. But with this, they would be healed within 2 script executions.

Is there a way for doing this??

Thanks for your help in advance.
Aline

Aline September 01, 2009 06:31

Comments

1 comment

Hello Aline,

There is no control over the way that SQL Compare formats the code that it produces, although I agree it would be interesting to combine SQL Prompt layout and SQL Compare scripting.

Using IF EXISTS...DROP has been a request that has been around for awhile. It's still a feature request at this point though, sorry to say. (SC-2909)

Brian Donahue September 02, 2009 10:19

0

Add comment

Please sign in to leave a comment.

How can we help you today?

configuration for &quot;modeling&quot; the scripts

Comments