I was wondering if anyone could help me with something that I've noticed now that we've upgraded our SQL version from 2005 to 2012. We have a number of stored procedures that pass in a list of INT IDs from the application and the developers generally call a stored procedure from inside the main stored procedure to put the values in the table. The stored proc is called GetTableIntFromString and does a loop through the string to put it in the table. This doesn't cause any issues in 2005, but when I point SSMS at a SQL 2005 database and run one of these stored procedure that calls this looping stored procedure, I don't get the plan for the nested stored proc call.
When I look at the same query plan pointed at an SQL 2012 database, for the nested proc call, I get the entire plan for the proc call including every time through the loop in the query plan for the main proc. The problem I run into is that this either makes the query plan so big that it errors before I can see the whole plan or at the very least makes for a lot more scrolling while looking at the plan.
Is there any way to make the query plan output from the 2012 database not display the full plan for the nested proc call? If I need to look at how the nested one is performing, it's easy enough to do on it's own, I don't need to see the full thing every time it's used especially since it's making things that I do need to see not appear.