Create and Drop table everyday [duplicate]

Question

This question already has answers here:

Creating tables dynamically at runtime (5 answers)

Closed 8 years ago.

My Customer want to create new table everyday, e.g. MyTable<yyyymmdd>, and then my application will read this table and do some cross-check. After done all cross-check, I need to drop this table. Every day will be create and drop table.

Is it good solution? could be database will crash because of this?

please advice me.

• i already give another solution, which customer just insert the data into one table. After that, I'll delete all records once done. But customer refuse to use my solution.

Answer 1

There is no point in creating and dropping the table with the same columns everyday. If the columns in that table are changing everyday you can go ahead with the approach.

Your database will not crash because of this. Just make sure that services are not accessing the table when it is dropped.

Answer 2

this is a simple life cycle issue. use interval partitioning. easy to manage, good for performance.