Yep, you could use a transaction like this:

begin tran

:r "C:\sqlscripts\01.script1.sql"

if (@@error != 0) goto endRollback

...

Yes, the resulting script must be run in SQLCMD mode.

The ability to include .sql files into other .sql files is really useful and SQLCMD certainly has more features I should...

Thanks for sharing the .bat code.

For daily scripts deployment on multiple databases, I usually build a SQLCMD script in 2 steps:

1. Copy the .sql file paths into a new file,...