Stored Procedure Scripting

Brian DonahueBrian Donahue Posts: 6,590 New member
edited April 19, 2004 7:47AM in SQL Compare Previous Versions
Hi Scott,

We'll see what we can do!

Regards,

Brian Donahue
Red Gate Technical Support

"Scott Tucholka" <[email protected]> wrote in message
news:[email protected]
> We are having a problem with how the stored procedures are being scripted.
> We need an option that we could set that would always check for the
> existence of a procedure, drop it, and then always create the stored
> procedure. When we create builds, we do not have the option of our clients
> installing them sequentially since we send them enhancements to the older
> version before they install the newer version.
>
>
>
> Example: Version 1
>
> Create SP1 as .
>
>
>
> Example: Version 2
>
> Create SP2 as .
>
>
>
> Example: Version 1a (enhancement)
>
> Create SP2 as .
>
>
>
> As you can see, the client will install Version 1 and then Version 1a.
When
> they try to install Version 2, an error will occur since the stored
> procedure already exists.
>
>
>
> For some reason, we did not seem to have this problem prior to SQL Compare
> 3.x. If you need additional information, please ask.
>
>
>
> Scott Tucholka
> AQS
>
>
This discussion has been closed.