suggestion: drop object option

Brian Donahue

Hi Josh,

This would help people who want to generate one SQL script to update a
few different versions of the same database.

Regards,

Brian Donahue
Red Gate Technical Support

"Josh Nelson" <joshua.nelson@usap.gov> wrote in message
news:Lfh8l4HLEHA.1240@server53...
> Support:
>
> I am not sure where to post this, so I'll try here. If there would be a
> better place to provide you with enhancement requests/suggestions, I'd
love
> to know.
>
> I'd like to suggest that you offer an option when scripting differences
> between at least views, stored procs, and functions, that you can also
> script a DROP for the objects if by chance the object exists by the time
you
> run the update script.
>
> I've run into some scenarios where a developer moved a stored proc or view
> over to the destination DB between the time I ran the comparison tools and
> the time I was able to apply the script. Obviously this is a bit of a
> process issue on our end, but it would be nice I at least had that
scripting
> option.
>
> Thanks for the great product...keep up the good work!
>
> ~Josh Nelson
>
>

Brian Donahue

Hi Jim,

It's looking less likely now. The inefficiency of dropping and
re-creating would cause problems such as connection timeouts and the like.
We may implement this as an option, but not in the short term.

Thanks,

Brian Donahue
Red Gate Technical Support


"Jim" <jim@nospam.com> wrote in message news:kYl1YAQPEHA.1220@server53...
> I too have requested this feature. It would be a big help and would
> definitely help the resulting scripts from the compare to be more
> "resilient" in the event the database it was being applied to was slightly
> different. In the real world we run into this fairly often where a
database
> has been manually modified to address an issue that will later be taken
care
> of with a full update. If you don't remember this then full update fails
on
> that clients system because the object already exists.
>
>
> "Brian Donahue (Red Gate)" <brian.donahue@red-gate.com> wrote in message
> news:eHlEJBULEHA.2488@server53...
> > Hi Josh,
> >
> > This would help people who want to generate one SQL script to update
a
> > few different versions of the same database.
> >
> > Regards,
> >
> > Brian Donahue
> > Red Gate Technical Support
> >
> > "Josh Nelson" <joshua.nelson@usap.gov> wrote in message
> > news:Lfh8l4HLEHA.1240@server53...
> > > Support:
> > >
> > > I am not sure where to post this, so I'll try here. If there would be
a
> > > better place to provide you with enhancement requests/suggestions, I'd
> > love
> > > to know.
> > >
> > > I'd like to suggest that you offer an option when scripting
differences
> > > between at least views, stored procs, and functions, that you can also
> > > script a DROP for the objects if by chance the object exists by the
time
> > you
> > > run the update script.
> > >
> > > I've run into some scenarios where a developer moved a stored proc or
> view
> > > over to the destination DB between the time I ran the comparison tools
> and
> > > the time I was able to apply the script. Obviously this is a bit of a
> > > process issue on our end, but it would be nice I at least had that
> > scripting
> > > option.
> > >
> > > Thanks for the great product...keep up the good work!
> > >
> > > ~Josh Nelson
> > >
> > >
> >
> >
>
>

pthistleton

Since I have asked for this also, just thought I would join the thread and say this would help me out a lot. Whether as a default or as an option it is a feature I need as I am essentially doing what JLIEN is and dumping the SQL Compare script through a custom parser to add the conditional drops and changing the alters to creates.