title: are continous insert and delete operations on a single database table a valid design?
body: <p>i have an application, where in for every request on reaching the application server, all its attributes are stored in a particular table with a unique request Id. And on completion of the processing of the request(i.e., on generation of the response but before sending the response to the client), based on the unique request id, the corresponding row is deleted from the table. Now, an application on an average can process a very large of number of requests. So this means a huge amount of insert operations and then corresponding delete operations on a single table.Will it affect the database performance and its stability ?</p>