Archives of the TeradataForum
Message Posted: Mon, 17 May 1999 @ 19:30:12 GMT
| Subj: || || Re: Temporary tables for Microstrategy |
| From: || || John Hall |
I can understand why the DROP TABLE was to be avoided (although it's much, much better under V2R2). My real question is how to manage
all these temporary tables.
Does Microstrategy always empty the temporary tables? If so, then I understand that there's no reason to keep them. Do the people who
use Microstrategy put all of these temporary tables into a purpose-specific database and then have a scheduled job that performs a DELETE
DATABASE on that database? I don't have a problem with this approach, I'm just wondering if that's the way it's done in the real-world.
If Microstrategy always empties the temporary table when it's done with the table, then the volatile temporary tables is probably a good
solution. If the contents of the temporary table is kept (as I said, I haven't worked with Microstrategy), then the volatile temporary
table won't exist beyond the session in which the volatile temporary table was created and therefore can't be used. If that were the case,
then Microstrategy would have to be smart enough to know whether a temporary table needs to be kept beyond a session.