In the previous post, I showed that even though a partition was “removed” (ie, exchanged out) from a table, a query running against the table could still successfully run the completion.
However, of course, if once that partition is exchanged out, it is now a table in it’s own right…and is subject to the whims of what a DBA may wish to do with it. If that table is dropped, or truncated, then as you might expect, our query is going to struggle to find that data ! ![]()
Here’s an example of what happens when the query cannot successfully run:




Leave a reply to Sam Cancel reply