What are the challenges you face when working across database platforms? Take the survey

Unscripting Stored Procedures?

Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
edited June 4, 2004 1:04PM in SQL Compare Previous Versions
Hi Lasse,

You probably want to filter out all of the stored procedures before
producing the synchronization. The best way to do that is to click the
'select all' button from the toolbar, then click off the objects on the
object filter toolbar so you're shown nothing but the stored procedures,
then click the 'select none' button. That selects everything but the stored

I'd check to make sure you've got the latest version of the software as
well because we've done a lot of work on improving the dependency-order


Brian Donahue
Red Gate Technical Support

"Lasse Jensen" <redgate@lundby.net> wrote in message
> We are evaluating the SQL bundle and using to script significant changes
> across two different versions of a complex database, with 100's of tables
> and 1000's of stored procedures. We would like a way to stop SQL Compare
> from scripting the changes to stored procedures and cannot work out how to
> do it in this product - can you help?
> FYI: The synchronisation file is currently 20MB, and the code to add and
> alter the SP's is interwoven with other changes so it's very hard to
> delete the various statements. The main reason we have to filter out the
> SP's is that we've encountered 100's of errors when we try to run the
> script, as it seems the script tries to apply changes in an order that
> conflicts with the existing constraints etc. While I'd like to work with
> to investigate why the current script has problems, we think we can create
> workaround by running parts of the sync script, provided that we can
> the code related to the SP's (as they form the bulk of the 20MB of
> changes...)
> Thanks
> Lasse & Julian (copenhagen)
This discussion has been closed.