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

Turning off transactions

Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
edited November 9, 2005 7:50AM in SQL Compare Previous Versions
Hi John,

Thanks for your enquiry. I think that this is possible, but if there's a
failed transaction early-on in the script, wouldn't you like to fix the
problem rather than letting the script make a partial migration of the
schema? If you want throw caution to the wind, you could take the T-SQL
statements out of the script.

I hope this helps!

Brian Donahue

Technical Support Engineer

Red Gate Software Ltd.

44 870 1600 037

mailto:brian.donahue@red-gate.com


"John West" <nospam@nospam.com> wrote in message
news:dwyKJNd4CHA.1184@server53...
> It'd be convenient if we could turn off the wrapping of all objects within
> transactions. Because dependencies are so fickle, scripts to create
views,
> sps and functions have some failures. I'd like the ones that were created
> successfully to be kept, not removed because others failed.
>
> Any chance of this option being added?
>
> Thanks,
> John
>
>

Comments

  • Options
    Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
    FYI -- SQL Compare version 3 and up now have a Do not include plumbing for transactional synchronization scripts option. This will allow you to generate scripts that will not roll back (undo) if an error occurs.
This discussion has been closed.