I have a DDL script that builds up a database for development, dropping
and creating domains, generators, tables, procedures and company.

When modifying this script, I frequently introduce errors, which I then
discover by running the script from isql.exe using the INPUT command.

As the objects build one upon another, a failure to create an object
will result in the creation of depending objects to also fail, leading
to an unnecessary proliferation of error messages, which wouldn't be
there if not for the root cause, i.e. the error I introduced.

Is there a way to instruct the INPUT command, or the server, to abort
processing on the first error instead of trucking on down the script?

--
Michael Ludwig