Can you 'batches' be stored procedures. Then you could do what you want.

>>>1) return from an ENTIRE script instead of just a batch within the script?
>>
>>From within the QA, Dan has provided the only option which will require that you do not use multiple batchs. Now if your going to run the script from OSQL, you can raise an error using RAISERROR with a state of 127.
>
>unfortunately - these are run from QA and have lots and lots of batches ...
>
>>
>>>2)call one sql script from within another?
>>
>>There is nothing built into the product to do this. And if there was, it would require that the installed script was located on the same box as SQL Server.
>
>that would be fine - these are for field updates of databases - controlled by our staff
>
>Tx,