(teddysnips@hotmail.com) writes:
> However, the text box where I can enter the SQL truncates at 231
> characters.
>
> What can I do, short of running the job myself? Can I split it into
> two or more tasks? If so, where should I split it? And can I
> establish a dependency between them so that, in the event of one task
> failing, the other(s) don't execute.

But the script in a file and the run the job as a command-line job that
fires up the script with ISQL.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp