Batch objects are unique to SQL-Programmer.  We are all familiar with batches.   We create them everyday and execute them.  Batches that we run frequently get stored as files on a workstation.  What happens if your workstation blows up?   You probably aren't backing up your workstation.  What if more than one person wants to use them?  What if someone makes a modification to one and doesn't pass it around to everyone else?  Batch objects eliminate this by storing batches on your SQL Server so that they get backed up along with your databases and are available for common use.  In order to store batch objects, you have to enable it first.  This can be done from SQL-Explorer or Access Manager.  The documentation states that you have to be sa to do this, but that is not correct.  All you have to have is create table permissions for the database you are enabling batch objects for.  When you enable batch objects, a table named SQL_Programmer_Objects will be created.  When you save a batch object, it is stored in this table.

SQL-Programmer IX SP2 with TSQL Debugger 1 2 3 4 5 6 7 8 9 10 11 12