Lynn Pettis (4/29/2016)

---

Brandie Tarvin (4/29/2016)

---

Luis Cazares (4/29/2016)

---

Or install more memory.

Umm, that won't work. SSMS has the memory limitation. Not my desktop.

Per Microsoft:

Note SSMS is a 32-bit process. Therefore, it is limited to 2 GB of memory. SSMS imposes an artificial limit on how much text that can be displayed per database field in the results window. This limit is 64 KB in "Grid" mode and 8 KB in "Text" mode. If the result set is too large, the memory that is required to display the query results may surpass the 2 GB limit of the SSMS process. Therefore, a large result set can cause the error that is mentioned in the "Symptoms" section.

Sigh. The problem with all of these solutions (I just realized) is that it doesn't allow me to pick around the jobs I don't want to script out. That's kind of why I wanted to use the right-click version.

Now I have to spend time hunting through the code (when I get it working) to remove the DROPs that I don't want to drop. I suppose that's less time then the copy-n-paste stuff, but I wanted to make this faster.

SQLCMD is the alternative at that point. I have had massively long scripts that I could read and edit in SSMS but would not run. Running them using SQLCMD, however, works.