While trying to get the execution plan for a stored procedure, I get the above error. I drop these keys prior to truncating the tables, then reload the tables and add the keys back. This should not generate an error in the execution plan, should it? If so, why?
By swshurts 21 asked Apr 16, 2013 at 02:06 PM
I was saying that, but based on the analysis of the SQL Sentry Plan Explorer, I got carried away when it suggested that the indices were a bottleneck when I was loading the temp tables. So, I decided to drop the primary keys, along with the indices. Bad idea...
I have converted the primary keys on the temporary tables to indices and it works much better...
Thanks for your responses. ,Never mind... I should be using indexes for the table.
By swshurts 21 answered Apr 16, 2013 at 02:27 PM