Schedule maitenance or temp tables

[Shawn]

I'm developing a content management system to use for the
web. I want to allow users to alter data, delete data,
and add data for each individual user so that when a new
user comes to the area, they will have a clean slate to
start from opposed to seeing what the other users have
done. If I do use temp tables, they will only be vaild
until the user session expires, correct?

Is the best way to accomplish that by using temp tables or
should I schedule a truncate table at periodic intervals?

Thanks a million!!!

[Aaron Bertrand - MVP]

> Is the best way to accomplish that

Accomplish what? How long do you want the data to persist? How often do
you want to clean it out?

[Shawn]

Well I want every new user that comes to the website to be
able to give the system a test run with their own data.
So I guess my best solution would be to create it with
temp tables. But then the problem I see is that each time
a user comes to the website, behind the scenes the
overhead of creating the temp tables and stored procedures
come into play.

Currently I have it to where anyone can add, modify,
delete content from the system, but once they leave I
don't want their data to persist. So instead of making
temp tables, should I just datetimestamp when they altered
data then delete all the data for the day or use temp
tables?

>-----Original Message-----

>> Is the best way to accomplish that

>
>Accomplish what? How long do you want the data to

persist? How often do

>you want to clean it out?
>
>
>.
>