EXECUTE SQL Task and pasting code. Will it fit?

Use caution when pasting code in an EXECUTE SQL TASK in SSIS; there is a limit to the number of lines that you can enter. I never knew this until I started putting more and more code in it, only to find out the hard way. What I did was paste code, then if I needed to add more, I'd open it, paste into SSMS, edit, and then paste back into the window. Pasting code into these things should be avoided anyway - use the file connection as the SQLSourceType to maintain a stealthy method for TSQL in your packages. This little window should be used for TSQL such as LINQ should be for accessing data. Small amounts and minimally. Looking at Books Online, I see nothing at all that mentions the size of input into this task. I was happily working away one day and noticed that as fast as I would paste the code it would disappear.

Relying on this task for a lot of TSQL script is like using the old enterprise manager window to write stored procedures. If you recall, the Enterprise Manager in SQL Server 7 and 2000 used to allow you to enter (and edit) code directly in the stored procedure window. This essentially did an ALTER PROCEDURE on the stored proc, and was a quick and dirty way, mostly dirty, to edit code. Unfortunately it wreaked havoc on managing source control, and if you happened to use the date on the procedure, you were disappointed because the ALTER didn't change the datetime stamp that the proc was compiled. Only a DROP and CREATE did. In other words, it was a lousy place to create and edit code...and likewise the EXECUTE SQL Task window.

I pasted some text with a line counter in the window, and here's what I got - I tried to put 1000 lines in there by the way:

---------------------

BOL doesn't always have the answers, does it?