We had the same issue in Fox when we devised this method. In Fox we had a remedy for that. We had an object up at runtime that tracked the building of our calculated cursors ( temp tables ) and before each view ( or temp table is built that is based on other temp tables ) is run we check to see if the temp tables need updating based on any other data changing ( via the UI ). We run this process through meta data so it is quite automated. I can see us having the same method on the server. Also, several of our temp tables are just runtime copies of a static data images that does not change it is just there for us to join to for speeding up the queries. Som eof the tabales are created then destroyed once used as well to prevent collisions.