Yep, it's a limit on the system. That's an extremely large number of queries to have within a single stored procedure.
You could use extended events to capture each individual execution plan for each statement. That's how I'd solve the problem of getting the plans. You could also use a server-side trace to do the same thing, but it's going to put more of a load on the system than extended events will.
answered May 02 '12 at 12:30 PM
Grant Fritchey ♦♦
1,100 queries... that doesn't make it very easy to troubleshoot does it?
I'm not sure if this will do the job for you but from the SSMS menu open Query->Query Options...
answered May 02 '12 at 12:29 PM